Revoke a Wiki.js API key by id.
AI agents call wiki_apikey_revoke to permanently remove resources in Mcp Wikijs Mv — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Revoking an API key is an irreversible action that permanently invalidates credentials. Any system or user relying on that key loses access immediately, and the key cannot be un-revoked. This is a destructive, non-reversible operation with potentially high blast radius if a key used by automated systems or multiple users is revoked.
From the tool's definition Revoke a Wiki.js API key by id
Attacks that exploit this kind of access
Revoke a Wiki.js API key by id. It is categorised as a Destructive tool in the Mcp Wikijs Mv MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Wikijs Mv MCP server in PolicyLayer and add a rule for wiki_apikey_revoke: 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 Mcp Wikijs Mv. Nothing to install.
wiki_apikey_revoke 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 wiki_apikey_revoke 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 wiki_apikey_revoke. 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.
wiki_apikey_revoke is provided by the Mcp Wikijs Mv MCP server (janschachtschabel/mcp-for-wiki-js). 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 →