Get one cookie by cookie_id with full value (subject to a hard cap to keep output bounded).
AI agents call interceptor_browser_get_cookie to retrieve information from Proxy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves sensitive authentication and session cookies from a browser intercepted by the MITM proxy. While it performs a read-only operation (no data is modified), the severity is high because cookies often contain session tokens, authentication credentials, or tracking identifiers that could enable account compromise, session hijacking, or impersonation if exposed to an untrusted agent.
From the tool's definition Tool name 'interceptor_browser_get_cookie' and description 'Get one cookie by cookie_id with full value' indicate data retrieval without modification. The action is a query operation that retrieves stored cookie values.
Documented attack patterns abuse exactly the kind of access interceptor_browser_get_cookie gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Proxy, and nothing reaches the server without passing your rules. This is the rule we recommend for interceptor_browser_get_cookie:
{
"version": "1",
"default": "deny",
"tools": {
"interceptor_browser_get_cookie": {}
}
}interceptor_browser_get_cookie 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.
Get one cookie by cookie_id with full value (subject to a hard cap to keep output bounded). It is categorised as a Read tool in the Proxy MCP Server, which means it retrieves data without modifying state.
Register the Proxy MCP server in PolicyLayer and add a rule for interceptor_browser_get_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 Proxy. Nothing to install.
interceptor_browser_get_cookie 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 interceptor_browser_get_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 interceptor_browser_get_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.
interceptor_browser_get_cookie is provided by the Proxy MCP server (yfe404/proxy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Proxy, 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.
89 Proxy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.