AI agents call clear_session to permanently remove resources in Frisco MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing a saved session is irreversible: the authentication session data is destroyed and cannot be recovered. The user would need to log in again. Closing the browser also terminates any in-progress state. This is a destructive operation on session data, though the blast radius is moderate (limited to session/auth state, not financial data or files).
From the tool's definition 'Clears the saved session and closes the browser' — permanently removes the saved session state
Documented attack patterns abuse exactly the kind of access clear_session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Frisco MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_session:
{
"version": "1",
"default": "deny",
"hide": [
"clear_session"
]
} clear_session disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Clears the saved session and closes the browser. It is categorised as a Destructive tool in the Frisco MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Frisco MCP server in PolicyLayer and add a rule for clear_session: 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 Frisco MCP. Nothing to install.
clear_session 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 clear_session 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 clear_session. 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.
clear_session is provided by the Frisco MCP server (mkidawa/frisco-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Frisco MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Frisco MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.