save_symphony · Composer Trade MCP: Risk & Policy

WHAT IT DOES

What save_symphony does on Composer Trade

AI agents use save_symphony to create or update resources in Composer Trade — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Composer Trade environment.

WHY IT NEEDS A POLICY

Why save_symphony needs a policy

This tool modifies investment strategy configurations reversibly. It creates or updates strategy data (symphonies) without executing trades or permanently deleting data, placing it in Write. Severity is high because saved strategies directly influence trading behavior and portfolio composition.

From the tool's definition Tool name 'save_symphony' on a server that 'create[s], backtest[s], and trade[s] automated investing strategies (symphonies).' The verb 'save' indicates creation or modification of strategy definitions that persist.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_symphony Rate-limited

save_symphony stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_symphony": {
      "limits": [
        {
          "counter": "save_symphony_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 save_symphony

What does the save_symphony tool do? +

save_symphony. It is categorised as a Write tool in the Composer Trade MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_symphony? +

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

What risk level is save_symphony? +

save_symphony is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_symphony? +

Yes. Add a rate_limit block to the save_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.

How do I block save_symphony completely? +

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

What MCP server provides save_symphony? +

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