AI agents use cookie_set to create or update resources in MCP Camoufox — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Camoufox environment.
Setting cookies is a write operation as it creates or modifies data (session cookies, authentication tokens, tracking identifiers). While reversible via cookie_delete, cookies can be weaponized to hijack sessions, impersonate users, or maintain unauthorized access.
From the tool's definition Tool description: 'Set a cookie.' The tool creates or modifies session state by setting cookies, which are reversible but can affect authentication, session hijacking, or tracking.
Documented attack patterns abuse exactly the kind of access cookie_set gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Camoufox, and nothing reaches the server without passing your rules. This is the rule we recommend for cookie_set:
{
"version": "1",
"default": "deny",
"tools": {
"cookie_set": {
"limits": [
{
"counter": "cookie_set_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}cookie_set 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.
Set a cookie. It is categorised as a Write tool in the MCP Camoufox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Camoufox MCP server in PolicyLayer and add a rule for cookie_set: 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 MCP Camoufox. Nothing to install.
cookie_set 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 cookie_set 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 cookie_set. 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.
cookie_set is provided by the MCP Camoufox MCP server (robithyusuf/mcp-camoufox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Camoufox, 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.
102 MCP Camoufox tools catalogued and risk-classified — across an index of 43,000+ MCP servers.