Get token transfer history
AI agents call get_token_transfers to retrieve information from Web3 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical token transfer records from the blockchain. It performs no state changes, does not execute code or transactions, and cannot modify, delete, or create data. The risk is informational disclosure only—an agent could learn about token flows but cannot execute transfers, spend funds, or cause irreversible damage.
From the tool's definition Tool name 'get_token_transfers' and description 'Get token transfer history' indicate data retrieval with no modification capability. The verb 'Get' and the noun 'history' signal a read-only query operation.
Documented attack patterns abuse exactly the kind of access get_token_transfers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Web3, and nothing reaches the server without passing your rules. This is the rule we recommend for get_token_transfers:
{
"version": "1",
"default": "deny",
"tools": {
"get_token_transfers": {}
}
}get_token_transfers 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 token transfer history. It is categorised as a Read tool in the Web3 MCP Server, which means it retrieves data without modifying state.
Register the Web3 MCP server in PolicyLayer and add a rule for get_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 Web3. Nothing to install.
get_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 get_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 get_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.
get_token_transfers is provided by the Web3 MCP server (tumf/web3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Web3, 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.
17 Web3 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.