apikeys_revoke_api_key
⚠️ DESTRUCTIVE — requires human confirmation before use in automated pipelines. Permanently revoke a DataNexus API key. The key will stop working immediately. This action cannot be undone — generate a new key if access is needed again.
This record as markdown: /tools/dev-7bd0-mcp-server/apikeys-revoke-api-key.md
What apikeys_revoke_api_key does on DataNexus MCP
AI agents call apikeys_revoke_api_key to permanently remove resources in DataNexus MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | — | API key (dnx_...) to permanently revoke. Required. |
Parameters from the server's own tool schema.
Why apikeys_revoke_api_key is rated Critical
Revoking an API key is an irreversible operation that cannot be recovered without manual intervention (generating a new key). This fits the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone'.
From the tool's definition Tool description explicitly states '⚠️ DESTRUCTIVE' and 'Permanently revoke a DataNexus API key' with 'This action cannot be undone'. Revocation is irreversible and immediately terminates access.
Attacks that exploit this kind of access
The rule that runs apikeys_revoke_api_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DataNexus MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For apikeys_revoke_api_key, this is the rule to start with:
apikeys_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 DataNexus MCP, apply this rule, and every apikeys_revoke_api_key call is checked against it from then on.
Questions about apikeys_revoke_api_key
⚠️ DESTRUCTIVE — requires human confirmation before use in automated pipelines. Permanently revoke a DataNexus API key. The key will stop working immediately. This action cannot be undone — generate a new key if access is needed again. It is categorised as a Destructive tool in the DataNexus MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
apikeys_revoke_api_key accepts 1 parameter: key. The full parameter table on this page comes from the server's own tool schema.
Register the DataNexus MCP server in PolicyLayer and add a rule for apikeys_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 DataNexus MCP. Nothing to install.
apikeys_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 apikeys_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 apikeys_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.
apikeys_revoke_api_key is provided by the DataNexus MCP server (dev-7bd0/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DataNexus, and thousands of servers like it.
Across the catalogue