AI agents invoke run_backtest to trigger actions in Wyckoff Trading Agent MCP Server. 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.
Backtesting involves running algorithmic simulations against historical market data, which is an Execute operation—it triggers external computational processes whose outcomes depend on input parameters (stock selections, time periods, strategy parameters).
From the tool's definition Tool name 'run_backtest' combined with context of a Wyckoff trading analysis server indicates execution of backtesting simulations. The sibling tool 'run_funnel_simulation' confirms this server executes complex analytical operations.
Documented attack patterns abuse exactly the kind of access run_backtest gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wyckoff Trading Agent MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_backtest:
{
"version": "1",
"default": "deny",
"tools": {
"run_backtest": {
"limits": [
{
"counter": "run_backtest_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_backtest 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.
Free to start. No card required.
run_backtest. It is categorised as a Execute tool in the Wyckoff Trading Agent MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wyckoff Trading Agent MCP Server MCP server in PolicyLayer and add a rule for run_backtest: 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 Wyckoff Trading Agent MCP Server. Nothing to install.
run_backtest is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_backtest 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.
Set action: deny in the PolicyLayer policy for run_backtest. 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.
run_backtest is provided by the Wyckoff Trading Agent MCP Server MCP server (youngcan-wang/wyckofftradingagent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Wyckoff Trading Agent MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Wyckoff Trading Agent MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.