api_key_delete
Delete an API key by its numeric ID. Use api_key_list to find the ID. This immediately revokes access for anyone using that key.
This record as markdown: /tools/nasbridge/api-key-delete.md
What api_key_delete does on Nasbridge
AI agents call api_key_delete to permanently remove resources in Nasbridge, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why api_key_delete is rated Critical
This tool irreversibly deletes an API key, which cannot be undone. The deletion immediately revokes access, making it a destructive action that cannot be recovered. While the severity is high rather than critical (it affects authentication rather than data), the irreversible nature and potential for disrupting legitimate users' access places it squarely in the Destructive category, which takes precedence over Write.
From the tool's definition Delete an API key by its numeric ID. This immediately revokes access for anyone using that key.
Attacks that exploit this kind of access
The rule that runs api_key_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For api_key_delete, this is the rule to start with:
api_key_delete 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 Nasbridge, apply this rule, and every api_key_delete call is checked against it from then on.
Questions about api_key_delete
Delete an API key by its numeric ID. Use api_key_list to find the ID. This immediately revokes access for anyone using that key. It is categorised as a Destructive tool in the Nasbridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nasbridge MCP server in PolicyLayer and add a rule for api_key_delete: 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 Nasbridge. Nothing to install.
api_key_delete 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 api_key_delete 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 api_key_delete. 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.
api_key_delete is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
Across the catalogue