Clear all session data for a session ID.
AI agents call session_clear to permanently remove resources in Atlas — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool destroys session state without recovery or undo capability. In a clinical FHIR document context, session data may contain user context, authentication state, or references to sensitive medical information. While not directly modifying patient records, clearing all session data is an irreversible operation that cannot be undone, fitting the Destructive category.
From the tool's definition Tool name 'session_clear' and description 'Clear all session data for a session ID' explicitly indicate irreversible deletion of session data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all session data for a session ID. It is categorised as a Destructive tool in the Atlas MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Atlas MCP server in PolicyLayer and add a rule for session_clear: 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 Atlas. Nothing to install.
session_clear 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_clear 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_clear. 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_clear is provided by the Atlas MCP server (rsanandres/atlas_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 →