Get recent transfers for a specific RWA token
AI agents call get_token_transfers to retrieve information from RWA Pipe 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 historical transfer data about RWA tokens without creating, modifying, deleting, or executing any state-changing operations. It is a read-only query similar to other sibling tools (get_holder_balance, get_contract_profile, etc.) that fetch blockchain data.
From the tool's definition Tool name 'get_token_transfers' and description 'Get recent transfers for a specific RWA token' both indicate a query/retrieval operation with no modification or execution of external actions.
Attacks that exploit this kind of access
Get recent transfers for a specific RWA token. It is categorised as a Read tool in the RWA Pipe MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RWA Pipe MCP Server 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 RWA Pipe MCP Server. 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 RWA Pipe MCP Server MCP server (rwapipe/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 →