KnowBe4 (BYOK)

KnowBe4 (BYOK) — connector documentation

• MCP endpoint: https://byok-knowbe4.connectorbay.com/mcp
• REST API: POST https://byok-knowbe4.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-knowbe4.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own KnowBe4 KnowBe4 Reporting API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-knowbe4.connectorbay.com/health · Tool schemas: https://byok-knowbe4.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-knowbe4 · agent@connectorbay.com

What KnowBe4 (BYOK) is for

KnowBe4 (BYOK) lets an AI assistant read your own KnowBe4 data through the KnowBe4 API with a key you supply (KnowBe4 Reporting API key). Read-only: 11 tools (get_account, get_account_risk_history, list_groups, list_users, get_user, list_phishing_campaigns, list_phishing_security_tests, list_training_campaigns, list_training_enrollments, list_training_store_purchases, list_training_policies). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to us.api.knowbe4.com, eu.api.knowbe4.com, ca.api.knowbe4.com, uk.api.knowbe4.com, de.api.knowbe4.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by KnowBe4. KnowBe4 and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "What subscription level and risk score does our KnowBe4 account have?"
• "How has our KnowBe4 risk score changed over time?"
• "Which KnowBe4 groups do we have and which has the highest risk score?"
• "Which active KnowBe4 users have the highest risk score?"
• "Show KnowBe4 user 1234"
• "What phishing campaigns have we run in KnowBe4 and how did they do?"

What it does

• get_account: Show the KnowBe4 account: name, subscription level and end date, seat count, current organisation risk score and admin contacts.
• get_account_risk_history: Show the organisation's risk score over time (six months by default, or the full history).
• list_groups: List KnowBe4 groups with type, member count, current risk score and status.
• list_users: List KnowBe4 users with name, job title, department, location, risk score, phish-prone percentage and status. Contact numbers are not returned.
• get_user: Get one KnowBe4 user's profile and risk score by user id (no contact numbers).
• list_phishing_campaigns: List phishing simulation campaigns with status, frequency, last phish-prone percentage and the security tests each has run.
• list_phishing_security_tests: List phishing security tests (individual simulation sends) with aggregate counts of delivered, opened, clicked, reported and data-entered.
• list_training_campaigns: List security awareness training campaigns with status, dates, groups, content modules and completion percentage.
• list_training_enrollments: List training enrollments with module, campaign, status, dates and time spent, filtered by campaign, module or user id. Names and emails are not returned.
• list_training_store_purchases: List training content (modules, videos, policies) the account has purchased or has access to, with type, duration and retirement status.
• list_training_policies: List the policies available for acknowledgement training with minimum reading time, default language and status.

BYOK key

You bring your own KnowBe4 KnowBe4 Reporting API key (https://developer.knowbe4.com/rest/reporting/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to us.api.knowbe4.com, eu.api.knowbe4.com, ca.api.knowbe4.com, uk.api.knowbe4.com, de.api.knowbe4.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://developer.knowbe4.com/rest/reporting/ (the API this connector calls, with a BYOK key)

Live from the KnowBe4 API (us.api.knowbe4.com, eu.api.knowbe4.com, ca.api.knowbe4.com, uk.api.knowbe4.com, de.api.knowbe4.com) with a BYOK key; documentation: https://developer.knowbe4.com/rest/reporting/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by KnowBe4. KnowBe4 and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your KnowBe4 account.

Built for: Worldwide. Languages: English.

KnowBe4 (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What KnowBe4 (BYOK) is. KnowBe4 (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own KnowBe4 data: Read your KnowBe4 phishing campaigns, security tests, training campaigns, enrollments, groups, users and risk scores with your own reporting API key. You bring your own KnowBe4 KnowBe4 Reporting API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one KnowBe4 call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to us.api.knowbe4.com, eu.api.knowbe4.com, ca.api.knowbe4.com, uk.api.knowbe4.com, de.api.knowbe4.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If KnowBe4 rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What KnowBe4 receives. The request we make on your behalf, including the key and the arguments, under KnowBe4's own terms and privacy policy. KnowBe4 acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer KnowBe4 gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your KnowBe4 data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. KnowBe4 (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at KnowBe4 at any time to end all access.

Children. KnowBe4 (BYOK) is a general-audience service operated by the adult using the assistant, under KnowBe4's own age rules.

Changes. We will post changes here with a new effective date.

KnowBe4 (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the KnowBe4 (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. KnowBe4 (BYOK) provides: Read your KnowBe4 phishing campaigns, security tests, training campaigns, enrollments, groups, users and risk scores with your own reporting API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own KnowBe4 credentials and only access data you are allowed to access. KnowBe4's terms apply to your use of KnowBe4; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by KnowBe4. KnowBe4 and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data KnowBe4 returns, lightly trimmed; it may be incomplete, delayed or changed by KnowBe4. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your KnowBe4 account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent KnowBe4's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; KnowBe4 may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your KnowBe4 key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action KnowBe4 takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-knowbe4

KnowBe4 (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-knowbe4.connectorbay.com/mcp
• REST API: https://byok-knowbe4.connectorbay.com/openapi.json
• Live status: https://byok-knowbe4.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. KnowBe4 (BYOK) never asks for them.