ログアウトして保存されたトークンを削除します
AI agents use verge_logout to create or update resources in Verge MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Verge MCP Server environment.
This tool modifies stored authentication tokens by deleting them, which is a reversible state change (the user can log back in). It does not execute arbitrary code, delete permanent data, move money, or perform irreversible destructive operations on content. It is categorized as Write because it modifies the authentication session state.
From the tool's definition Tool name 'verge_logout' and description 'ログアウトして保存されたトークンを削除します' (logs out and deletes saved token) indicates modification of authentication state and token storage.
Attacks that exploit this kind of access
ログアウトして保存されたトークンを削除します. It is categorised as a Write tool in the Verge MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Verge MCP Server MCP server in PolicyLayer and add a rule for verge_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 Verge MCP Server. Nothing to install.
verge_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 verge_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 verge_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.
verge_logout is provided by the Verge MCP Server MCP server (tomohirof/verge-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 →