Composer Trade

24 tools. 13 can modify or destroy data without limits.

8 destructive tools with no built-in limits. Policy required.

Last updated:

13 can modify or destroy data
11 read-only
24 tools total

Community server · catalogue entry verified 30/06/2026

How to control Composer Trade ↓

What Composer Trade exposes to your agents

Read (11) Write / Execute (5) Destructive / Financial (8)
Critical Risk

The most dangerous Composer Trade tools

13 of Composer Trade's 24 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Composer Trade

PolicyLayer is an MCP gateway — it sits between your AI agents and Composer Trade, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default
{
  "cancel_invest_or_withdraw": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Rate limit write operations
{
  "save_symphony": {
    "limits": [
      {
        "counter": "save_symphony_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get_account_holdings": {
    "limits": [
      {
        "counter": "get_account_holdings_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Composer Trade — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON COMPOSER TRADE →

Instant setup, no code required.

All 24 Composer Trade tools

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Composer Trade

Can an AI agent move money through the Composer Trade MCP server? +

Yes. The Composer Trade server exposes 8 financial tools including cancel_invest_or_withdraw, cancel_single_trade, create_symphony. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How do I prevent bulk modifications through Composer Trade? +

The Composer Trade server has 2 write tools including save_symphony, update_saved_symphony. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Composer Trade.

How many tools does the Composer Trade MCP server expose? +

24 tools across 5 categories: Destructive, Execute, Financial, Read, Write. 11 are read-only. 13 can modify, create, or delete data.

How do I enforce a policy on Composer Trade? +

Register the Composer Trade MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Composer Trade tool call.

Deterministic rules across all 24 Composer Trade tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

24 Composer Trade tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.