run_backtest · FactorHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_backtest does on FactorHub MCP Server

AI agents invoke run_backtest to trigger actions in FactorHub 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.

WHY IT NEEDS A POLICY

Why run_backtest needs a policy

This tool executes complex backtesting algorithms whose effects depend on input parameters (strategy selection, date ranges, risk parameters). While it does not directly modify financial positions or delete data, backtesting is a computational operation that triggers external calculations and can consume significant resources.

From the tool's definition Tool name 'run_backtest' and description phrase '执行量化策略回测' (execute quantitative strategy backtest) indicate execution of code/algorithms.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_backtest Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_backtest": {
      "limits": [
        {
          "counter": "run_backtest_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 FactorHub MCP Server, so you can run agents against it safely.

FAQ

Questions about run_backtest

What does the run_backtest tool do? +

执行量化策略回测。内置策略：limit_up_first_board(涨停首板)、low_valuation(低估值)、momentum(动量)、mean_reversion(均值回归)。返回年化收益、夏普比率、最大回撤等。. It is categorised as a Execute tool in the FactorHub MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_backtest? +

Register the FactorHub 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 FactorHub MCP Server. Nothing to install.

What risk level is run_backtest? +

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

Can I rate-limit run_backtest? +

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.

How do I block run_backtest completely? +

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.

What MCP server provides run_backtest? +

run_backtest is provided by the FactorHub MCP Server MCP server (michaelfeng/factorhub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.