logout
Log out of Deloc and clear stored credentials. Use this to switch to a different account.
This record as markdown: /tools/deloc-mcp/logout.md
What logout does on Deloc
AI agents call logout to permanently remove resources in Deloc, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why logout is rated Critical
Logging out and clearing stored credentials is an irreversible local destructive action: the stored credentials are deleted/purged from the system. While no remote data is destroyed, the credential state cannot be recovered without re-authenticating. This is more severe than a simple write and fits Destructive due to the permanent removal of stored auth data.
From the tool's definition 'Log out of Deloc and clear stored credentials' — clears/destroys stored authentication credentials irreversibly
Attacks that exploit this kind of access
The rule that runs logout safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deloc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For logout, this is the rule to start with:
logout is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Deloc, apply this rule, and every logout call is checked against it from then on.
Questions about logout
Log out of Deloc and clear stored credentials. Use this to switch to a different account. It is categorised as a Destructive tool in the Deloc MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Deloc 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 Deloc. 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 Deloc MCP server (delocdev/deloc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deloc, and thousands of servers like it.
Across the catalogue