check_symphony_approval
Checks if the Symphony protocol has sufficient allowance to spend a specific token for a swap.
This record as markdown: /tools/testinguser1111111-sei-mcp-server/check-symphony-approval.md
What check_symphony_approval does on SEI MCP Server V2
AI agents call check_symphony_approval to retrieve information from SEI MCP Server V2 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_symphony_approval is rated Low
This tool performs a read-only check of blockchain allowance state. It queries existing approval data but does not execute swaps, modify approvals, transfer funds, or trigger transactions. The operation is informational only, supporting downstream decision-making by DeFi agents. No irreversible actions or financial movements occur.
From the tool's definition Tool name 'check_symphony_approval' and description 'Checks if the Symphony protocol has sufficient allowance' - uses 'Checks' which indicates a query/inspection operation with no state modification.
Attacks that exploit this kind of access
The rule that runs check_symphony_approval safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SEI MCP Server V2, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_symphony_approval, this is the rule to start with:
check_symphony_approval is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SEI MCP Server V2, apply this rule, and every check_symphony_approval call is checked against it from then on.
Questions about check_symphony_approval
Checks if the Symphony protocol has sufficient allowance to spend a specific token for a swap. It is categorised as a Read tool in the SEI MCP Server V2 MCP Server, which means it retrieves data without modifying state.
Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for check_symphony_approval: 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.
check_symphony_approval is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_symphony_approval 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 check_symphony_approval. 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.
check_symphony_approval 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.
More on SEI MCP Server V2, and thousands of servers like it.
This server
Across the catalogue