Delete a session permanently.
AI agents call session_delete to permanently remove resources in Iris MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes session data, which cannot be undone. Permanent deletion of state or session information is an irreversible action that could disrupt ongoing work, coordination, or communication across project teams. In the context of a cross-project coordination server, deleting a session could eliminate important context or break active collaborations.
From the tool's definition Tool name is 'session_delete' and description states 'Delete a session permanently.' The word 'permanently' and 'delete' indicate irreversible removal of data.
Attacks that exploit this kind of access
Delete a session permanently. It is categorised as a Destructive tool in the Iris MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Iris MCP server in PolicyLayer and add a rule for session_delete: 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 Iris MCP. Nothing to install.
session_delete 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_delete 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_delete. 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_delete is provided by the Iris MCP server (jenova-marie/iris-mcp). 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 →