Clear the current authentication session and stored tokens. Use this if you need to force a re-authentication.
AI agents call clear_session to permanently remove resources in LibreLink MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly destroys the current authentication session and deletes stored tokens. While not catastrophic, it is a destructive action (tokens/session are cleared/deleted) that cannot be undone—re-authentication would be required afterward. It is not merely a 'write' because the deletion of session tokens is a one-way operation with no rollback.
From the tool's definition Clear the current authentication session and stored tokens
Attacks that exploit this kind of access
Clear the current authentication session and stored tokens. Use this if you need to force a re-authentication. It is categorised as a Destructive tool in the LibreLink MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LibreLink MCP Server MCP server in PolicyLayer and add a rule for clear_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 LibreLink MCP Server. Nothing to install.
clear_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 clear_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 clear_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.
clear_session is provided by the LibreLink MCP Server MCP server (sedoglia/librelink-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 →