create_symphony
AI agents use create_symphony to commit financial operations through Composer Trade — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Even though the description is empty, the server context makes clear that symphonies are automated investing strategies. Creating one can commit financial obligations by setting up live trading logic. Given sibling tools that execute trades and manage portfolios, a newly created symphony could immediately or automatically affect real funds. Financial is the most severe applicable category.
From the tool's definition Tool name 'create_symphony' on a server described as enabling users to 'create, backtest, and trade automated investing strategies (symphonies) on Composer' — creating a symphony likely initiates an automated trading strategy with real financial implications.
Attacks that exploit this kind of access
create_symphony. It is categorised as a Financial tool in the Composer Trade MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Composer Trade MCP server in PolicyLayer and add a rule for create_symphony: 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 Composer Trade. Nothing to install.
create_symphony 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 create_symphony 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 create_symphony. 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.
create_symphony is provided by the Composer Trade MCP server (tanwithme/composer-trade-mcp). 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 →