withdraw_from_symphony
AI agents use withdraw_from_symphony to commit financial operations through Composer Trade — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves money from an investment symphony (portfolio), which is a direct financial transaction that commits financial obligations and reallocates capital. Even without a detailed description, the name unambiguously indicates a withdrawal operation on a financial account. An LLM agent misusing this tool could withdraw funds without authorization or at inappropriate times, causing direct financial loss.
From the tool's definition Tool name 'withdraw_from_symphony' combined with server's stated purpose to enable 'trade automated investing strategies' and presence of sibling tools 'cancel_invest_or_withdraw' and 'execute_single_trade' indicate financial operations.
Attacks that exploit this kind of access
withdraw_from_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 withdraw_from_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.
withdraw_from_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 withdraw_from_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 withdraw_from_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.
withdraw_from_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 →