batch_exit_analysis · Tradeblocks MCP: Risk & Policy

WHAT IT DOES

What batch_exit_analysis does on Tradeblocks

AI agents invoke batch_exit_analysis to trigger actions in Tradeblocks. 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 batch_exit_analysis needs a policy

batch_exit_analysis triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_exit_analysis Rate-limited

batch_exit_analysis 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": {
    "batch_exit_analysis": {
      "limits": [
        {
          "counter": "batch_exit_analysis_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 Tradeblocks, so you can run agents against it safely.

FAQ

Questions about batch_exit_analysis

What does the batch_exit_analysis tool do? +

Analyze how a candidate exit policy would perform across multiple trades in a block. Replays each matching trade, evaluates exit triggers against the minute-level P&L path, and returns aggregate statistics (win rate, Sharpe, profit factor, drawdown) comparable to get_statistics. Includes per-trigger attribution showing which triggers drive outcomes. Reads option-leg quotes via QuoteStore and underlying bars via SpotStore (cache only); trades with missing data are skipped. Use the data-pipeline tools to backfill cache, and strategy profiles to iterate on exit rules. It is categorised as a Execute tool in the Tradeblocks MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on batch_exit_analysis? +

Register the Tradeblocks MCP server in PolicyLayer and add a rule for batch_exit_analysis: 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 Tradeblocks. Nothing to install.

What risk level is batch_exit_analysis? +

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

Can I rate-limit batch_exit_analysis? +

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

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

batch_exit_analysis is provided by the Tradeblocks MCP server (tradeblocks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.