get_aggregate_symphony_stats

Get stats for every symphony in a brokerage account.

Server Composer Trade tanwithme/composer-trade-mcp
Category Read
Risk class Low
Parameters 00 required

What get_aggregate_symphony_stats does on Composer Trade

AI agents call get_aggregate_symphony_stats to retrieve information from Composer Trade without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_aggregate_symphony_stats needs a policy

This tool retrieves statistics about symphonies (automated investment strategies) from a brokerage account. The verb 'Get' and the absence of any language suggesting modification, deletion, or financial transactions confirm this is a read-only operation. It has no blast radius—an LLM agent calling this tool cannot cause harm to investments, accounts, or financial positions.

From the tool's definition Tool name 'get_aggregate_symphony_stats' and description 'Get stats for every symphony in a brokerage account' indicate a retrieval operation that queries data without modification or side effects.

Risk signalsBulk/mass operation — affects multiple targets

Questions about get_aggregate_symphony_stats

What does the get_aggregate_symphony_stats tool do? +

Get stats for every symphony in a brokerage account. It is categorised as a Read tool in the Composer Trade MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_aggregate_symphony_stats? +

Register the Composer Trade MCP server in PolicyLayer and add a rule for get_aggregate_symphony_stats: 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.

What risk level is get_aggregate_symphony_stats? +

get_aggregate_symphony_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_aggregate_symphony_stats? +

Yes. Add a rate_limit block to the get_aggregate_symphony_stats 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 get_aggregate_symphony_stats completely? +

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.