revoke_access_key

Revoke an existing access key. Revoked keys cannot be used for signing

SERVERTempo SOURCEarome3/tempo-mcp

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/arome3-tempo-mcp/revoke-access-key.md

WHAT IT DOES

What revoke_access_key does on Tempo

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

RISK

Why revoke_access_key is rated Critical

Revoking an access key is a destructive operation—once executed, the key cannot be restored without regeneration through other means, and it immediately and permanently blocks the key's ability to sign transactions.

From the tool's definition Tool description states 'Revoke an existing access key' which permanently disables an authentication credential.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs revoke_access_key safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tempo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For revoke_access_key, this is the rule to start with:

revoke_access_key Hidden

revoke_access_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_access_key"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about revoke_access_key

What does the revoke_access_key tool do? +

Revoke an existing access key. Revoked keys cannot be used for signing. It is categorised as a Destructive tool in the Tempo 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_access_key? +

Register the Tempo MCP server in PolicyLayer and add a rule for revoke_access_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 Tempo. Nothing to install.

What risk level is revoke_access_key? +

revoke_access_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_access_key? +

Yes. Add a rate_limit block to the revoke_access_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_access_key completely? +

Set action: deny in the PolicyLayer policy for revoke_access_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_access_key? +

revoke_access_key is provided by the Tempo MCP server (arome3/tempo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tempo, and thousands of servers like it.

This server

All 61 Tempo tools → Critical-risk tools on this server →

Across the catalogue

web3_revoke_key on 0xarchive →deauthorize_ssh_key on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →