Kenso MCP tools

Agent Permissions agent_permissions

What Ken may do on its own in the workspace, per action: asks_first (Ken asks a person first) or runs_on_its_own (no per-item approval; every other guard stays). update changes only the actions it names, after the user says yes; switching send_email or send_linkedin to runs_on_its_own is for a person in the Kenso app only. Needs the agent_permissions flag.

Call it from an MCP client connected to https://mcp.ken.so/mcp: reads go through agent_permissions_read and changes through agent_permissions_write. Each takes operation plus that operation's parameters, and your workspace role decides which operations you see.

Each operation with a route calls the Kenso API at https://api.ken.so with Authorization: Bearer <Kenso API key>, Ken-Version: 1.1 and X-Ken-Workspace-Id: <workspace id>. You can call that route directly with the same headers.

Operations: get, update

get

Read. Early access: needs agent_permissions on for the workspace. GET https://api.ken.so/v1/agent-permission-settings

Return what Ken may do on its own in the workspace: each action's mode, asks_first or runs_on_its_own. Always all seven actions. Needs the agent_permissions flag; never a Client seat.

GET /api/v1/agent-permission-settings. Public where the agent_permissions flag is on. Sends Ken-Version 1.1.
client_id is sent as X-Ken-Workspace-Id.
Returns data.permissions, one entry per action in page order (send_email, send_linkedin, research_accounts,
scan_signals, build_assets, run_crm_workflows, book_meetings), each with:
- mode: asks_first (Ken asks a person before it acts) or runs_on_its_own (Ken acts without a per-item approval;
  every other guard, such as suppression, limits, sending windows and client approvals, still applies). The stored
  mode, else the default: send_email, send_linkedin and build_assets ask first, the others run on their own.
- available: false while Kenso does not follow this action's mode yet; its mode cannot change then.
- lockedReason: reply_agent_not_autonomous on book_meetings while the reply agent is off or not autonomous (it
  then reads asks_first, which is not the stored mode: do not send it back in an update unless you mean to store
  asks_first), else null.
- updatedAt: when the mode was last set, null for an action the workspace never set.
And data.clientWorkspace: true for a workspace run for a client.
These modes decide what Ken does unattended; they do not limit what you do with your own role.
404 not_found where the agent_permissions flag is off.

update

Write. Early access: needs agent_permissions on for the workspace. PATCH https://api.ken.so/v1/agent-permission-settings

Body (json): permissions array

Set the mode of the named actions; actions left out stay as they are. Each entry is {action, mode} (clientYes for a client workspace's sends). Requires `workspace_settings`.

PATCH /api/v1/agent-permission-settings. Public where the agent_permissions flag is on. Sends Ken-Version 1.1 and
X-Ken-Actor: agent. Consent scope workspace:admin.
permissions: [{"action": "scan_signals", "mode": "asks_first"}], at least one entry, each action at most once.
action is send_email, send_linkedin, research_accounts, scan_signals, build_assets, run_crm_workflows or
book_meetings. mode is asks_first (Ken asks a person before it acts) or runs_on_its_own (Ken acts without a
per-item approval; every other guard still applies). These modes decide what Ken does unattended; they do not
limit what you do with your own role. Only change a mode after the user says yes.
Switching send_email or send_linkedin to runs_on_its_own from here is refused (403 approval_requires_human,
before any 400): it removes a person's approval of each send, and only a person in the Kenso app can do that.
Switching one of them back to asks_first, and every other action either way, works from here.
Returns every action after the change, as get does. A mode that does not change writes nothing; each change is
recorded in the workspace's audit log. Errors (nothing is saved): 400 validation_failed with details[].code
required, unknown_action, unknown_mode, duplicate_action, action_not_available (Kenso does not follow this action
yet), reply_agent_not_autonomous (book_meetings set to runs_on_its_own while the reply agent is not on and
autonomous, even when it already reads that way) or client_yes_required; 404 not_found where the
agent_permissions flag is off.