KnowBe4 MCP integration for AI agents.
Connect AI agents to KnowBe4 through 5 structured actions, including get account, get group, and get user. Review authentication, inputs, workflows, and safe…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the KnowBe4 integration exposes
The KnowBe4 Agent App exposes 5 provider-backed actions for security work. Its current contract lets an authorized agent get knowbe4 account and subscription data from the reporting api, get a specific knowbe4 group by group id, and get a specific knowbe4 user by user id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected KnowBe4 account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real KnowBe4 capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_accountREADGet KnowBe4 account and subscription data from the Reporting API.
get_groupREADGet a specific KnowBe4 group by group ID.
INPUTS: groupId
get_userREADGet a specific KnowBe4 user by user ID.
INPUTS: userId
list_groupsREADList KnowBe4 groups with optional status, per_page, and cursor filters.
INPUTS: status / perPage / cursor
list_usersREADList KnowBe4 users with optional status, group, expanded group, per_page, and cursor filters.
INPUTS: status / groupId / expandGroups / perPage / cursor
INPUT CONTRACTS
Know what the action needs before it runs.
get_group
groupIdOPTIONAL- KnowBe4 group ID.
get_user
userIdOPTIONAL- KnowBe4 user ID.
list_groups
statusOPTIONAL- Optional KnowBe4 record status filter.
perPageOPTIONAL- Maximum number of records to request from KnowBe4.
cursorOPTIONAL- KnowBe4 cursor value returned by a previous request.
list_users
statusOPTIONAL- Optional KnowBe4 record status filter.
groupIdOPTIONAL- Only return users who are members of this KnowBe4 group ID.
expandGroupsOPTIONAL- Whether to ask KnowBe4 to expand group details on each user.
perPageOPTIONAL- Maximum number of records to request from KnowBe4.
cursorOPTIONAL- KnowBe4 cursor value returned by a previous request.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account
Get KnowBe4 account and subscription data from the Reporting API. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_accountVerify with Get Group
Get a specific KnowBe4 group by group ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_groupSAFETY BOUNDARY
Operate KnowBe4 with explicit limits
- Authorize KnowBe4 with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned KnowBe4 data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in KnowBe4 rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the KnowBe4 task completed successfully.
CONNECTION MODEL
API key
KnowBe4 Reporting API key sent as a Bearer token. Generate it in the Reporting API Management Console: https://training.knowbe4.com/app/api_tokens/reporting.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by KnowBe4.