Retrieve all cookies for the current page context as a JSON array. Use when the user wants to inspect cookies, debug authentication state, check session tokens, or verify that cookies were set correctly. For setting individual cookies, use pilot_set_cookie; for bulk import from a real browser, us...
AI agents call pilot_cookies to retrieve information from Pilot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns cookie data (name, value, domain, path, session tokens, etc.) without modifying any state. However, the data returned can be highly sensitive — it includes session tokens and authentication cookies — meaning misuse could expose credentials or allow session hijacking, warranting a medium severity despite being read-only.
From the tool's definition Retrieve all cookies for the current page context as a JSON array
Documented attack patterns abuse exactly the kind of access pilot_cookies 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_cookies:
{
"version": "1",
"default": "deny",
"tools": {
"pilot_cookies": {}
}
}pilot_cookies is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve all cookies for the current page context as a JSON array. Use when the user wants to inspect cookies, debug authentication state, check session tokens, or verify that cookies were set correctly. For setting individual cookies, use pilot_set_cookie; for bulk import from a real browser, use pilot_import_cookies. Parameters: (none) Returns: JSON array of cookie objects with name, value, domain, path, expires, httpOnly, secure, and sameSite attributes. Errors: None — returns empty array. It is categorised as a Read tool in the Pilot MCP Server, which means it retrieves data without modifying state.
Register the Pilot MCP server in PolicyLayer and add a rule for pilot_cookies: 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_cookies is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pilot_cookies 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_cookies. 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_cookies 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.