Transfer RBTC or ERC20 tokens on Rootstock blockchain between wallets
AI agents use transfer-tokens to commit financial operations through RSK MCP Server - Rootstock Blockchain Tools — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly transfers cryptocurrency (RBTC) or blockchain tokens (ERC20) between wallets. Such operations move financial assets and commit monetary obligations. Misuse by an AI agent could result in unauthorized fund transfers, loss of assets, or fraudulent transactions. This is the most severe category applicable, superseding Execute or Write classifications.
From the tool's definition Tool is explicitly named 'transfer-tokens' and described as 'Transfer RBTC or ERC20 tokens on Rootstock blockchain between wallets'.
Attacks that exploit this kind of access
Transfer RBTC or ERC20 tokens on Rootstock blockchain between wallets. It is categorised as a Financial tool in the RSK MCP Server - Rootstock Blockchain Tools MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the RSK MCP Server - Rootstock Blockchain Tools MCP server in PolicyLayer and add a rule for transfer-tokens: 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 RSK MCP Server - Rootstock Blockchain Tools. Nothing to install.
transfer-tokens is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the transfer-tokens 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 transfer-tokens. 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.
transfer-tokens is provided by the RSK MCP Server - Rootstock Blockchain Tools MCP server (rsksmart/rsk-mcp-server). 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 →