AI agents use pilot_set_cookie to create or update resources in Pilot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pilot environment.
Setting cookies modifies browser storage state but is reversible (cookies can be deleted, updated, or cleared). This is a Write operation rather than Execute because it directly manipulates a specific data store rather than executing arbitrary code or triggering external operations.
From the tool's definition Tool name is 'pilot_set_cookie' with description 'Set a cookie on the current page'. The verb 'set' indicates modification of browser state (cookies), which is reversible via deletion or modification.
Documented attack patterns abuse exactly the kind of access pilot_set_cookie gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pilot, and nothing reaches the server without passing your rules. This is the rule we recommend for pilot_set_cookie:
{
"version": "1",
"default": "deny",
"tools": {
"pilot_set_cookie": {
"limits": [
{
"counter": "pilot_set_cookie_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pilot_set_cookie 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 on the current page. It is categorised as a Write tool in the Pilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pilot MCP server in PolicyLayer and add a rule for pilot_set_cookie: 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 Pilot. Nothing to install.
pilot_set_cookie 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 pilot_set_cookie 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 pilot_set_cookie. 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.
pilot_set_cookie is provided by the Pilot MCP server (tacosyhorchata/pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 61 Pilot tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
61 Pilot tools catalogued and risk-classified — across an index of 42,500+ MCP servers.