Get, set, or clear cookies
AI agents call ira_cookies to permanently remove resources in IRA-RESEARCHER — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call ira_cookies doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from IRA-RESEARCHER is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Get, set, or clear cookies. It is categorised as a Destructive tool in the IRA-RESEARCHER MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the IRA-RESEARCHER MCP server in PolicyLayer and add a rule for ira_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 IRA-RESEARCHER. Nothing to install.
ira_cookies is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the ira_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 ira_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.
ira_cookies is provided by the IRA-RESEARCHER MCP server (neuralnexustech/ira-researcher). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →