session_reset
Reset the browser session to a clean state (about:blank, no cookies or storage).
This record as markdown: /tools/mcp-anything/session-reset.md
What session_reset does on Mcp Anything
AI agents call session_reset to permanently remove resources in Mcp Anything, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why session_reset is rated Critical
This tool irreversibly clears the browser session state including cookies and storage, returning it to a blank state. This is a destructive operation as it permanently wipes session data that cannot be recovered once cleared.
From the tool's definition Reset the browser session to a clean state (about:blank, no cookies or storage)
Attacks that exploit this kind of access
The rule that runs session_reset 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 session_reset, this is the rule to start with:
session_reset is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every session_reset call is checked against it from then on.
Questions about session_reset
Reset the browser session to a clean state (about:blank, no cookies or storage). It is categorised as a Destructive tool in the Mcp Anything MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Anything MCP server in PolicyLayer and add a rule for session_reset: 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.
session_reset 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 session_reset 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 session_reset. 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.
session_reset 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.
Across the catalogue