Store cookies and browser session state for a signup session in the KeyID vault.
Part of the KeyID server.
Free to start. No card required.
AI agents use save_browser_state to create or modify resources in KeyID. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call save_browser_state repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach KeyID.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"save_browser_state": {
"limits": [
{
"counter": "save_browser_state_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full KeyID policy for all 64 tools.
These attack patterns abuse exactly the kind of access save_browser_state gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Store cookies and browser session state for a signup session in the KeyID vault.. It is categorised as a Write tool in the KeyID MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the KeyID MCP server in PolicyLayer and add a rule for save_browser_state: 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 KeyID. Nothing to install.
save_browser_state 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 save_browser_state 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 save_browser_state. 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.
save_browser_state is provided by the KeyID MCP server (https://keyid.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 64 KeyID tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.