connections_setToolPolicy
Set tool policies (allow, approve or deny) (PATCH /v1/connections/{id}/tools)
This record as markdown: /tools/onesi-genesis-mcp/connections-settoolpolicy.md
What connections_setToolPolicy does on Genesis
AI agents use connections_setToolPolicy to create or update resources in Genesis, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Genesis environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Connection id (conn_ followed by 32 hex) |
body | object | Yes | |
approval | string | — | After a 428 APPROVAL_REQUIRED: the approval_request_id, once a human approved it in Auto. Sent as the OneOS-Approval header. |
Parameters from the server's own tool schema.
Why connections_setToolPolicy is rated Medium
An AI agent can call connections_setToolPolicy faster than any human can review: one bad instruction and it creates or modifies resources in Genesis by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs connections_setToolPolicy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For connections_setToolPolicy, this is the rule to start with:
connections_setToolPolicy stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Genesis, apply this rule, and every connections_setToolPolicy call is checked against it from then on.
Questions about connections_setToolPolicy
Set tool policies (allow, approve or deny) (PATCH /v1/connections/{id}/tools). It is categorised as a Write tool in the Genesis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
connections_setToolPolicy accepts 3 parameters: id, body, approval. Required: id, body. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for connections_setToolPolicy: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Genesis. Nothing to install.
connections_setToolPolicy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the connections_setToolPolicy rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for connections_setToolPolicy. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
connections_setToolPolicy is provided by the Genesis MCP server (@onesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genesis, and thousands of servers like it.
This server
Across the catalogue