Clear a specific saved session state or all states for this agent/session.
AI agents call clear_session_state to permanently remove resources in Agent MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (session states) that cannot be undone. While not as severe as financial or infrastructure-level destruction, clearing all session states could result in loss of important task history, context, and collaboration records. The 'all states' variant represents a high-blast-radius destructive action. Destructive is the appropriate category per severity hierarchy.
From the tool's definition Tool performs 'Clear' operation on saved session states, which is described as irreversibly removing specific or all state records for an agent/session. The use of 'clear' indicates deletion without recovery mechanism.
Documented attack patterns abuse exactly the kind of access clear_session_state gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_session_state:
{
"version": "1",
"default": "deny",
"hide": [
"clear_session_state"
]
}clear_session_state 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.
Clear a specific saved session state or all states for this agent/session. It is categorised as a Destructive tool in the Agent MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Agent MCP server in PolicyLayer and add a rule for clear_session_state: 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 Agent MCP. Nothing to install.
clear_session_state 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_state 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_state. 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_state is provided by the Agent MCP server (rinadelph/agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Agent MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Agent MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.