get_token_info
Get metadata for a TIP-20 token including name, symbol, decimals, and total supply.
This record as markdown: /tools/arome3-tempo-mcp/get-token-info.md
What get_token_info does on Tempo
AI agents call get_token_info to retrieve information from Tempo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_token_info is rated Low
This tool only retrieves and returns token metadata—information that is static and publicly available on a blockchain. It does not create, modify, delete, or execute any operations. Even in the context of a stablecoin payment system, querying token information poses minimal security risk as it cannot be misused to cause financial harm, data loss, or unauthorized actions.
From the tool's definition Tool description states 'Get metadata for a TIP-20 token including name, symbol, decimals, and total supply.' The verb 'Get' and the focus on retrieving immutable metadata (name, symbol, decimals, total supply) indicates read-only data retrieval with no side…
Attacks that exploit this kind of access
The rule that runs get_token_info 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 get_token_info, this is the rule to start with:
get_token_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tempo, apply this rule, and every get_token_info call is checked against it from then on.
Questions about get_token_info
Get metadata for a TIP-20 token including name, symbol, decimals, and total supply. 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_token_info: 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_token_info 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_token_info 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_token_info. 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_token_info 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.
This server
Across the catalogue