revoke_api_key

Revoke (soft-delete) an API key by ID.

SERVERBusinys SOURCE@businys/mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/app-businys-mcp-server/revoke-api-key.md

What revoke_api_key does on Businys

AI agents call revoke_api_key to permanently remove resources in Businys, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why revoke_api_key is rated Critical

Revoking an API key is a destructive action that permanently invalidates authentication credentials. Even though described as a 'soft-delete' (not hard-deleted from database), the functional outcome is irreversible for the credential holder—the key becomes non-functional immediately and cannot be recovered.

From the tool's definition Tool name is 'revoke_api_key' with description 'Revoke (soft-delete) an API key by ID.' The term 'revoke' combined with 'soft-delete' indicates removal of authentication credentials, which irreversibly disables access and cannot be easily undone without…

Questions about revoke_api_key

What does the revoke_api_key tool do? +

Revoke (soft-delete) an API key by ID. It is categorised as a Destructive tool in the Businys MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on revoke_api_key? +

Register the Businys 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 Businys. Nothing to install.

What risk level is revoke_api_key? +

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.

Can I rate-limit revoke_api_key? +

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.

How do I block revoke_api_key completely? +

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.

What MCP server provides revoke_api_key? +

revoke_api_key is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Businys, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Businys's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.