High Risk →

place_trailing_twap_order

Place a trailing-then-TWAP order. When trail triggers, execute via TWAP. action: trailing_twap_sell|trailing_twap_buy.

High parameter count (10 properties)

Part of the Trade Router MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents invoke place_trailing_twap_order to trigger processes or run actions in Trade Router. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

place_trailing_twap_order can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-traderouter-trade-router-mcp.yaml
tools:
  place_trailing_twap_order:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Trade Router policy for all 21 tools.

Tool Name place_trailing_twap_order
Category Execute
Risk Level High

View all 21 tools →

Agents calling execute-class tools like place_trailing_twap_order have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

place_trailing_twap_order is one of the high-risk operations in Trade Router. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the place_trailing_twap_order tool do? +

Place a trailing-then-TWAP order. When trail triggers, execute via TWAP. action: trailing_twap_sell|trailing_twap_buy.. It is categorised as a Execute tool in the Trade Router MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on place_trailing_twap_order? +

Add a rule in your Intercept YAML policy under the tools section for place_trailing_twap_order. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Trade Router MCP server.

What risk level is place_trailing_twap_order? +

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

Can I rate-limit place_trailing_twap_order? +

Yes. Add a rate_limit block to the place_trailing_twap_order rule in your Intercept 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 place_trailing_twap_order completely? +

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

place_trailing_twap_order is provided by the Trade Router MCP server (@traderouter/trade-router-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Trade Router

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.