Transfer native tokens (Sei) to an address
AI agents use transfer_sei to commit financial operations through SEI MCP Server V2 — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves cryptocurrency (native Sei tokens) to specified addresses, committing financial obligations and transferring monetary value. While not strictly destructive of data, it permanently transfers assets and matches the Financial category definition of 'moves money or commits financial obligations.' The high severity reflects that a compromised AI agent could drain funds by sending tokens to arbitrary…
From the tool's definition Tool name 'transfer_sei' and description 'Transfer native tokens (Sei) to an address' directly indicates movement of cryptocurrency assets (native Sei tokens) to recipient addresses, which constitutes a financial transaction with irreversible effects.
Attacks that exploit this kind of access
Transfer native tokens (Sei) to an address. It is categorised as a Financial tool in the SEI MCP Server V2 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for transfer_sei: 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 SEI MCP Server V2. Nothing to install.
transfer_sei 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_sei 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_sei. 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_sei is provided by the SEI MCP Server V2 MCP server (testinguser1111111/sei-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 →