Revoke a cnk_* token by token_id. Rotates credentials without deactivating the agent. After revocation, calls using the old token return 401 immediately. TOKEN ROTATION WORKFLOW: 1. Call guard_onboard_agent or guard_register_agent -- get a fresh cnk_* token 2. Update the new cnk_* value in your n...
Part of the Clevername server.
Free to start. No card required.
AI agents may call guard_revoke_token to permanently remove or destroy resources in Clevername. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call guard_revoke_token in a loop, permanently destroying resources in Clevername. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"guard_revoke_token"
]
}See the full Clevername policy for all 67 tools.
These attack patterns abuse exactly the kind of access guard_revoke_token gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Revoke a cnk_* token by token_id. Rotates credentials without deactivating the agent. After revocation, calls using the old token return 401 immediately. TOKEN ROTATION WORKFLOW: 1. Call guard_onboard_agent or guard_register_agent -- get a fresh cnk_* token 2. Update the new cnk_* value in your n8n HTTP Header credential 3. Call guard_revoke_token with the OLD token's token_id FINDING token_id: Call guard_list_agents -- each agent has token_id (UUID) and token_hint (first 8 chars of cnk_*). Match token_hint to identify the right token. token_id != the cnk_* string itself. If you only have the cnk_* string: match its first 8 chars against token_hint.. It is categorised as a Destructive tool in the Clevername MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Clevername MCP server in PolicyLayer and add a rule for guard_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 Clevername. Nothing to install.
guard_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 guard_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 guard_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.
guard_revoke_token is provided by the Clevername MCP server (@clevername/clevername-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 67 Clevername tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.