revoke_api_key

Permanently revoke an API key. Pass confirm: true to proceed — this is irreversible and any clients using this key will stop working immediately.

SERVERPostking Mcp SOURCEpostking-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-bitsandtea-postking-mcp/revoke-api-key.md

WHAT IT DOES

What revoke_api_key does on Postking Mcp

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

RISK

Why revoke_api_key is rated Critical

This tool irreversibly revokes API keys, disabling client authentication immediately with no recovery mechanism. While not data deletion, it permanently breaks access and functionality for systems relying on the key, matching the destructive pattern of irreversible, unrecoverable actions.

From the tool's definition Permanently revoke an API key. Pass confirm: true to proceed — this is irreversible and any clients using this key will stop working immediately.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs revoke_api_key safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Postking Mcp, 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 Hidden

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "revoke_api_key"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Postking Mcp, apply this rule, and every revoke_api_key call is checked against it from then on.

FAQ

Questions about revoke_api_key

What does the revoke_api_key tool do? +

Permanently revoke an API key. Pass confirm: true to proceed — this is irreversible and any clients using this key will stop working immediately. It is categorised as a Destructive tool in the Postking Mcp 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 Postking 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 Postking Mcp. 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 Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

What revoke_api_key does on Postking Mcp

Why revoke_api_key is rated Critical

The rule that runs revoke_api_key safely

Questions about revoke_api_key

More on Postking, and thousands of servers like it.