[ADMIN] Clear all cached sessions
AI agents call clear_sessions to permanently remove resources in Garza Home MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing all cached sessions destroys authentication state and active user sessions. This action cannot be undone without re-authentication, affecting all concurrent sessions system-wide. While not permanently deleting stored data, it forcefully terminates and invalidates active sessions, which constitutes a destructive action.
From the tool's definition Tool name 'clear_sessions' combined with description '[ADMIN] Clear all cached sessions' indicates irreversible deletion or invalidation of session data. The [ADMIN] designation signals privileged operation with broad impact.
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Attacks that exploit this kind of access
[ADMIN] Clear all cached sessions. It is categorised as a Destructive tool in the Garza Home MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Garza Home MCP server in PolicyLayer and add a rule for clear_sessions: 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 Garza Home MCP. Nothing to install.
clear_sessions 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_sessions 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_sessions. 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_sessions is provided by the Garza Home MCP server (itsablabla/garza-home-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 →