List, create, update, deactivate, or rotate agent keys. Manager only.
AI agents use manage_agent_keys to create or update resources in Writbase — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Writbase environment.
This tool modifies authentication material (agent keys) through creation, updates, and rotation. While deactivation is reversible (keys can be re-activated or recreated), the core operations are Write-category: creating new credentials and modifying existing ones. It does not permanently destroy data (Destructive) or execute arbitrary code (Execute).
From the tool's definition Tool description explicitly states it can 'create, update, deactivate, or rotate agent keys,' which are reversible modifications to authentication credentials. The 'Manager only' restriction indicates privileged access control.
Documented attack patterns abuse exactly the kind of access manage_agent_keys gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Writbase, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_agent_keys:
{
"version": "1",
"default": "deny",
"tools": {
"manage_agent_keys": {
"limits": [
{
"counter": "manage_agent_keys_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_agent_keys 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.
Free to start. No card required.
List, create, update, deactivate, or rotate agent keys. Manager only. It is categorised as a Write tool in the Writbase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Writbase MCP server in PolicyLayer and add a rule for manage_agent_keys: 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 Writbase. Nothing to install.
manage_agent_keys 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 manage_agent_keys 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 manage_agent_keys. 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.
manage_agent_keys is provided by the Writbase MCP server (https://{PROJECT_REF}.supabase.co/functions/v1/mcp-server/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Writbase, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Writbase tools catalogued and risk-classified — across an index of 43,000+ MCP servers.