Immediately revoke a scoped sub-key (DELETE /v1/keys/{key_id}). Root Bearer.
AI agents call lithtrix_keys_revoke to permanently remove resources in Lithtrix — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes authentication keys/credentials. Once revoked, a key cannot be recovered or undone. Unauthorized revocation of a sub-key could immediately block legitimate access to dependent systems or applications that rely on that key for authentication.
From the tool's definition Tool performs DELETE operation on cryptographic keys (/v1/keys/{key_id}). Description uses 'revoke' and 'DELETE' verb, indicating irreversible removal of authentication credentials. Requires 'Root Bearer' privilege, indicating high-sensitivity operation.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Immediately revoke a scoped sub-key (DELETE /v1/keys/{key_id}). Root Bearer. It is categorised as a Destructive tool in the Lithtrix MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Lithtrix MCP server in PolicyLayer and add a rule for lithtrix_keys_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 Lithtrix. Nothing to install.
lithtrix_keys_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 lithtrix_keys_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 lithtrix_keys_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.
lithtrix_keys_revoke is provided by the Lithtrix MCP server (lithtrix/lithtrix-mcp). 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 →