Transfer SOL from your keypair (using private key from .env) to another address
AI agents use transfer to commit financial operations through Web3 MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly transfers blockchain assets (SOL) using a private key, committing financial value to another address. This is irreversible and represents a direct financial obligation.
From the tool's definition Tool name is 'transfer' and description explicitly states 'Transfer SOL from your keypair...to another address', indicating it moves cryptocurrency (SOL tokens) from one account to another, which is a financial transaction.
Documented attack patterns abuse exactly the kind of access transfer gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Web3 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for transfer:
{
"version": "1",
"default": "deny",
"tools": {
"transfer": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to transfer is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Transfer SOL from your keypair (using private key from .env) to another address. It is categorised as a Financial tool in the Web3 MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Web3 MCP Server MCP server in PolicyLayer and add a rule for transfer: 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 MCP Server. Nothing to install.
transfer 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 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. 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 is provided by the Web3 MCP Server MCP server (strangelove-ventures/web3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 55 Web3 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
55 Web3 MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.