backtest_symphony_by_id · Composer Trade MCP: Risk & Policy

WHAT IT DOES

What backtest_symphony_by_id does on Composer Trade

AI agents invoke backtest_symphony_by_id to trigger actions in Composer Trade. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why backtest_symphony_by_id needs a policy

Based on the server context and sibling tool 'backtest_symphony', this tool likely runs a backtest simulation on an existing symphony by ID. Backtesting executes a computational process (running a simulation) but does not move money or modify live data. The empty description lowers confidence. Classified as Execute due to triggering an external computation/simulation operation.

From the tool's definition Tool name 'backtest_symphony_by_id' on a server that includes 'backtest_symphony' sibling tool; server description mentions backtesting automated investing strategies.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

backtest_symphony_by_id Rate-limited

backtest_symphony_by_id stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "backtest_symphony_by_id": {
      "limits": [
        {
          "counter": "backtest_symphony_by_id_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about backtest_symphony_by_id

What does the backtest_symphony_by_id tool do? +

backtest_symphony_by_id. It is categorised as a Execute tool in the Composer Trade MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on backtest_symphony_by_id? +

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

backtest_symphony_by_id is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit backtest_symphony_by_id? +

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

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

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