cookie_get
Get a cookie by name. Returns None if not found.
This record as markdown: /tools/mcp-anything/cookie-get.md
What cookie_get does on Mcp Anything
AI agents call cookie_get to retrieve information from Mcp Anything without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why cookie_get is rated Low
Cookie retrieval is a read-only operation that queries stored cookie data without modifying, deleting, or executing anything. The tool simply returns the cookie value or None, making it a Read category with low severity—minimal blast radius even if misused by an agent.
From the tool's definition The tool is named 'cookie_get' and the description states it 'Get[s] a cookie by name. Returns None if not found.' This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs cookie_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cookie_get, this is the rule to start with:
cookie_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every cookie_get call is checked against it from then on.
Questions about cookie_get
Get a cookie by name. Returns None if not found. It is categorised as a Read tool in the Mcp Anything MCP Server, which means it retrieves data without modifying state.
Register the Mcp Anything MCP server in PolicyLayer and add a rule for cookie_get: 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 Anything. Nothing to install.
cookie_get 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 cookie_get 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_get. 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_get is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Anything, and thousands of servers like it.
This server
Across the catalogue