revoke_role
Revoke a TIP-20 role from an address. Requires DEFAULT_ADMIN_ROLE on the token.
This record as markdown: /tools/arome3-tempo-mcp/revoke-role.md
What revoke_role does on Tempo
AI agents call revoke_role 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.
Why revoke_role is rated Critical
Revoking a role removes permissions/access rights from an address. This is effectively irreversible in impact (the address loses its capabilities immediately) and on a financial blockchain system, revoking key roles (e.g., minter, pauser, admin) could disrupt or permanently alter control of the token contract.
From the tool's definition 'Revoke a TIP-20 role from an address' — permanently removes an access control role, which is an irreversible administrative action that could strip critical permissions from addresses managing a stablecoin payment system.
Attacks that exploit this kind of access
The rule that runs revoke_role 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_role, this is the rule to start with:
revoke_role 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 Tempo, apply this rule, and every revoke_role call is checked against it from then on.
Questions about revoke_role
Revoke a TIP-20 role from an address. Requires DEFAULT_ADMIN_ROLE on the token. 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.
Register the Tempo MCP server in PolicyLayer and add a rule for revoke_role: 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.
revoke_role 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 revoke_role 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 revoke_role. 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.
revoke_role 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.
More on Tempo, and thousands of servers like it.
Across the catalogue