Get ERC20 token transfer history for an address
AI agents call telos_token_transfers to retrieve information from Telos Network MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays past transaction records, which is a read-only operation with no side effects. It does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an attacker could only gain visibility into token transfer history, not manipulate funds or trigger actions.
From the tool's definition Tool name 'telos_token_transfers' and description 'Get ERC20 token transfer history for an address' indicate a query operation that retrieves historical data without modifying or executing any state changes.
Attacks that exploit this kind of access
Get ERC20 token transfer history for an address. It is categorised as a Read tool in the Telos Network MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Telos Network MCP Server MCP server in PolicyLayer and add a rule for telos_token_transfers: 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 Telos Network MCP Server. Nothing to install.
telos_token_transfers 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 telos_token_transfers 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 telos_token_transfers. 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.
telos_token_transfers is provided by the Telos Network MCP Server MCP server (tairon-ai/telos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →