approve_symphony_token · SEI MCP Server V2 MCP

WHAT IT DOES

What approve_symphony_token does on SEI MCP Server V2

AI agents use approve_symphony_token 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.

WHY IT NEEDS A POLICY

Why approve_symphony_token needs a policy

This tool modifies blockchain state by setting a token approval/allowance, which is a Write operation. While reversible (allowances can be reset), it carries high severity because it grants spending authority that could enable subsequent unauthorized token transfers if an AI agent is compromised or misled into approving excessive amounts.

From the tool's definition Tool 'approves the Symphony protocol to spend a specific token' — this is a write operation that modifies on-chain token allowance state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

approve_symphony_token Rate-limited

approve_symphony_token stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "approve_symphony_token": {
      "limits": [
        {
          "counter": "approve_symphony_token_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches SEI MCP Server V2, so you can run agents against it safely.

FAQ

Questions about approve_symphony_token

What does the approve_symphony_token tool do? +

Approves the Symphony protocol to spend a specific token for swapping. This is a necessary step before swapping non-native tokens. 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.

How do I enforce a policy on approve_symphony_token? +

Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for approve_symphony_token: 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.

What risk level is approve_symphony_token? +

approve_symphony_token is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit approve_symphony_token? +

Yes. Add a rate_limit block to the approve_symphony_token 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.

How do I block approve_symphony_token completely? +

Set action: deny in the PolicyLayer policy for approve_symphony_token. 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.

What MCP server provides approve_symphony_token? +

approve_symphony_token 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.