grant_role

Grant a TIP-20 role to an address. Requires DEFAULT_ADMIN_ROLE on the token.

SERVERTempo SOURCEarome3/tempo-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/arome3-tempo-mcp/grant-role.md

WHAT IT DOES

What grant_role does on Tempo

AI agents use grant_role to create or update resources in Tempo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tempo environment.

RISK

Why grant_role is rated Medium

This tool grants privileged roles on a financial/stablecoin smart contract. While technically a 'write' operation (modifying access control state), the blast radius is critical: granting roles could allow an attacker to mint tokens, bypass compliance checks, blacklist/whitelist addresses, or perform other high-impact operations on the Tempo stablecoin system.

From the tool's definition Grant a TIP-20 role to an address. Requires DEFAULT_ADMIN_ROLE on the token.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs grant_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 grant_role, this is the rule to start with:

grant_role Rate-limited

grant_role stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "grant_role": {
      "limits": [
        {
          "counter": "grant_role_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about grant_role

What does the grant_role tool do? +

Grant a TIP-20 role to an address. Requires DEFAULT_ADMIN_ROLE on the token. It is categorised as a Write tool in the Tempo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on grant_role? +

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

What risk level is grant_role? +

grant_role is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit grant_role? +

Yes. Add a rate_limit block to the grant_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.

How do I block grant_role completely? +

Set action: deny in the PolicyLayer policy for grant_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.

What MCP server provides grant_role? +

grant_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.

KEEP EXPLORING

More on Tempo, and thousands of servers like it.

This server

All 61 Tempo tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →