AI agents use magnyxa_logout to create or update resources in Magnyxa — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Magnyxa environment.
The tool modifies authentication state and removes credentials (reversible operations: the user can re-authenticate). It does not destroy irreversible data or financial resources. While it affects security posture, deletion of tokens is a standard, expected authentication operation. Classified as Write rather than Destructive because token deletion is a normal, reversible logout flow that the user controls.
From the tool's definition Tool description states it logs out from Magnyxa and deletes saved authentication tokens (ログアウトして保存された認証トークンを削除します). This modifies stored credentials and session state.
Attacks that exploit this kind of access
Magnyxaからログアウトして保存された認証トークンを削除します。. It is categorised as a Write tool in the Magnyxa MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Magnyxa MCP server in PolicyLayer and add a rule for magnyxa_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 Magnyxa. Nothing to install.
magnyxa_logout is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the magnyxa_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 magnyxa_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.
magnyxa_logout is provided by the Magnyxa MCP server (@zelklab/magnyxa-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 →