Generates the transaction calldata for a swap without executing it.
AI agents use generate_symphony_swap_calldata to create or update resources in SEI MCP Server V2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SEI MCP Server V2 environment.
This tool generates calldata for financial transactions (token swaps) on the blockchain. Although it doesn't execute the transaction, calldata generation is a write operation that creates the structured data necessary to perform financial transactions.
From the tool's definition Generates transaction calldata for a swap. While not executing the swap itself, calldata generation is a preparatory write action that creates transaction data intended to modify blockchain state (moving tokens).
Attacks that exploit this kind of access
Generates the transaction calldata for a swap without executing it. It is categorised as a Write tool in the SEI MCP Server V2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for generate_symphony_swap_calldata: 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.
generate_symphony_swap_calldata is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_symphony_swap_calldata 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 generate_symphony_swap_calldata. 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.
generate_symphony_swap_calldata 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 →