revoke_api_key
Permanently revokes an API key. This is irreversible — the key will immediately stop working. Requires admin scope.
This record as markdown: /tools/de-agentview-agentview-mcp/revoke-api-key.md
What revoke_api_key does on agentView
AI agents call revoke_api_key to permanently remove resources in agentView, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
key_id | string | Yes | The ID of the key to revoke (from list_api_keys). |
access_token | string | — | Optional bearer token; prefer session_request_id. |
Parameters from the server's own tool schema.
Why revoke_api_key is rated Critical
Revoking an API key is an irreversible action that destroys the ability of systems or users to authenticate and access the agentview service. While not data deletion, it permanently disables a critical authentication credential and cannot be undone (a new key must be created instead). This fits the Destructive category as it is an action that cannot be reversed.
From the tool's definition Tool description explicitly states 'Permanently revokes an API key' and 'This is irreversible — the key will immediately stop working.' The use of 'Permanently' and 'irreversible' combined with the destructive action of disabling authentication credentials…
Risk signalsHandles credentials or secrets (access_token) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs revoke_api_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and agentView, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For revoke_api_key, this is the rule to start with:
revoke_api_key is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect agentView, apply this rule, and every revoke_api_key call is checked against it from then on.
Questions about revoke_api_key
Permanently revokes an API key. This is irreversible — the key will immediately stop working. Requires admin scope. It is categorised as a Destructive tool in the agentView MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
revoke_api_key accepts 2 parameters: key_id, access_token. Required: key_id. The full parameter table on this page comes from the server's own tool schema.
Register the agentView MCP server in PolicyLayer and add a rule for revoke_api_key: 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 agentView. Nothing to install.
revoke_api_key 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_api_key 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_api_key. 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_api_key is provided by the agentView MCP server (https://agentview.de/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on agentView, and thousands of servers like it.
Across the catalogue