This record as markdown: /tools/wavexis-mcp/wavexis-cookies-set.md
What wavexis_cookies_set does on Wavexis
AI agents use wavexis_cookies_set to create or update resources in Wavexis, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wavexis environment.
Why wavexis_cookies_set is rated Medium
Setting cookies modifies browser state reversibly (cookies can be cleared, updated, or deleted later). This is a Write operation. Severity is high because malicious cookie-setting can enable session hijacking, credential theft, tracking, or other attacks if an LLM agent is tricked into setting malicious cookies on behalf of a user or target.
From the tool's definition Tool name: 'wavexis_cookies_set'; description: 'Set a cookie in the browser.' — explicitly performs cookie creation/modification in browser state.
Attacks that exploit this kind of access
The rule that runs wavexis_cookies_set safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wavexis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wavexis_cookies_set, this is the rule to start with:
wavexis_cookies_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 Wavexis, apply this rule, and every wavexis_cookies_set call is checked against it from then on.
Questions about wavexis_cookies_set
Set a cookie in the browser. It is categorised as a Write tool in the Wavexis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wavexis MCP server in PolicyLayer and add a rule for wavexis_cookies_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 Wavexis. Nothing to install.
wavexis_cookies_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 wavexis_cookies_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 wavexis_cookies_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.
wavexis_cookies_set is provided by the Wavexis MCP server (MathiasPaulenko/wavexis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wavexis, and thousands of servers like it.
This server
Across the catalogue