cookie_set
A write tool on the Mcp Anything MCP server.
This record as markdown: /tools/mcp-anything/cookie-set.md
What cookie_set does on Mcp Anything
AI agents use cookie_set to create or update resources in Mcp Anything, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Anything environment.
Why cookie_set is rated Medium
Cookie setting creates or modifies browser/application state reversibly. This is a Write operation - it changes data but is not permanent (cookies can be cleared/modified). Severity is medium because cookie manipulation could affect authentication, tracking, or session state, but the impact depends on context and the specific cookies being set.
From the tool's definition Tool name 'cookie_set' indicates modification of cookie data. Description is empty, limiting certainty.
Attacks that exploit this kind of access
The rule that runs cookie_set 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_set, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every cookie_set call is checked against it from then on.
Questions about cookie_set
cookie_set is a write tool on the Mcp Anything MCP server. It is categorised as a Write tool in the Mcp Anything MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Anything 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 Anything. 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 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