Revoke an active embedded session.
AI agents call meshes_revoke_session to permanently remove resources in Mesheshq — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Revoking a session permanently invalidates it; the session cannot be restored once revoked. This is an irreversible destructive action. Misuse could terminate legitimate user or service sessions, causing disruption to integrations or workflows managed through the Meshes platform.
From the tool's definition 'Revoke an active embedded session' — revoking a session is an irreversible termination action that cannot be undone
Attacks that exploit this kind of access
Revoke an active embedded session. It is categorised as a Destructive tool in the Mesheshq MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mesheshq MCP server in PolicyLayer and add a rule for meshes_revoke_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 Mesheshq. Nothing to install.
meshes_revoke_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 meshes_revoke_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 meshes_revoke_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.
meshes_revoke_session is provided by the Mesheshq MCP server (mesheshq/meshes-mcp-server). 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 →