Logout from PocketBase and clear the authentication session. This invalidates the current token.
AI agents call logout to permanently remove resources in Ssakone Pocketbase — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Logging out invalidates the current authentication token and clears the session, which is an irreversible action — the token cannot be restored, only a new one can be obtained. However, the blast radius is low since it only affects the current session and a new login can be performed. It is more destructive than a simple write because the invalidation cannot be undone.
From the tool's definition 'Logout from PocketBase and clear the authentication session. This invalidates the current token.'
Attacks that exploit this kind of access
Logout from PocketBase and clear the authentication session. This invalidates the current token. It is categorised as a Destructive tool in the Ssakone Pocketbase MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ssakone Pocketbase MCP server in PolicyLayer and add a rule for logout: 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 Ssakone Pocketbase. Nothing to install.
logout 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 logout 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 logout. 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.
logout is provided by the Ssakone Pocketbase MCP server (@iflow-mcp/ssakone-pocketbase-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 →