吊销 API Token，使其立即失效。仅 admin 可调用。
AI agents call revoke_token to permanently remove resources in Agent-Comm-Hub — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Revoking a token is an irreversible destructive action — once revoked, the token is permanently invalidated and cannot be restored. Any agents or services relying on that token would immediately lose access. The admin-only restriction confirms the high blast radius, as misuse could disrupt multiple dependent services or agents in the multi-agent communication infrastructure.
From the tool's definition 吊销 API Token，使其立即失效 (Revoke API Token, making it immediately invalid)
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
吊销 API Token，使其立即失效。仅 admin 可调用。. It is categorised as a Destructive tool in the Agent-Comm-Hub MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Agent-Comm-Hub MCP server in PolicyLayer and add a rule for revoke_token: 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 Agent-Comm-Hub. Nothing to install.
revoke_token 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 revoke_token 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 revoke_token. 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.
revoke_token is provided by the Agent-Comm-Hub MCP server (liuboacean/agent-comm-hub). 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 →