Get all addresses that have a specific role on a TIP-20 token.
AI agents call get_role_members to retrieve information from Tempo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to retrieve role membership information from a blockchain token contract. It does not create, modify, delete, or execute any state-changing operations. While the server context involves financial operations (stablecoin payments), this specific tool is a simple data retrieval function with no direct financial impact or ability to trigger transactions.
From the tool's definition Tool name 'get_role_members' and description 'Get all addresses that have a specific role on a TIP-20 token' indicate a query operation that retrieves data without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_role_members gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tempo, and nothing reaches the server without passing your rules. This is the rule we recommend for get_role_members:
{
"version": "1",
"default": "deny",
"tools": {
"get_role_members": {}
}
}get_role_members is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all addresses that have a specific role on a TIP-20 token. It is categorised as a Read tool in the Tempo MCP Server, which means it retrieves data without modifying state.
Register the Tempo MCP server in PolicyLayer and add a rule for get_role_members: 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.
get_role_members is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_role_members 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 get_role_members. 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.
get_role_members 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.
Start from Tempo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
61 Tempo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.