backtest_strategy | PolicyLayer

WHAT IT DOES

What backtest_strategy does on PM-MCP (Portfolio Management MCP Server)

AI agents invoke backtest_strategy to trigger actions in PM-MCP (Portfolio Management 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 backtest_strategy needs a policy

Backtesting a strategy typically involves executing a simulation of trading logic against historical data, which can trigger complex computations and potentially automated trade signals or recommendations. Given the server context (AI-powered portfolio management), this tool likely runs analytical execution rather than simply reading data. However, the empty description significantly lowers confidence.

From the tool's definition Tool name 'backtest_strategy' on a portfolio management server; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

backtest_strategy Rate-limited

backtest_strategy 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": {
    "backtest_strategy": {
      "limits": [
        {
          "counter": "backtest_strategy_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 PM-MCP (Portfolio Management MCP Server), so you can run agents against it safely.

FAQ

Questions about backtest_strategy

What does the backtest_strategy tool do? +

backtest_strategy. It is categorised as a Execute tool in the PM-MCP (Portfolio Management 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 backtest_strategy? +

Register the PM-MCP (Portfolio Management MCP Server) MCP server in PolicyLayer and add a rule for backtest_strategy: 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 PM-MCP (Portfolio Management MCP Server). Nothing to install.

What risk level is backtest_strategy? +

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

Can I rate-limit backtest_strategy? +

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

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

backtest_strategy is provided by the PM-MCP (Portfolio Management MCP Server) MCP server (surplus96/pm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.