run_backtest_tool · KIS MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_backtest_tool does on KIS MCP Server

AI agents invoke run_backtest_tool to trigger actions in KIS 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_tool needs a policy

Backtesting tools execute algorithmic trading strategies against historical data, which constitutes code execution whose effects depend on strategy parameters and inputs. While not immediately destructive to live accounts, execution of financial strategies carries high blast radius if misused—an AI agent could execute poorly-designed or malicious trading strategies, leading to significant financial losses.

From the tool's definition Tool name 'run_backtest_tool' combined with server context describing 'automated strategy execution' and 'backtesting' indicates the tool triggers computational execution of trading strategies.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_backtest_tool Rate-limited

run_backtest_tool 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_tool": {
      "limits": [
        {
          "counter": "run_backtest_tool_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 KIS MCP Server, so you can run agents against it safely.

FAQ

Questions about run_backtest_tool

What does the run_backtest_tool tool do? +

run_backtest_tool. It is categorised as a Execute tool in the KIS 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_tool? +

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

What risk level is run_backtest_tool? +

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

Can I rate-limit run_backtest_tool? +

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

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

run_backtest_tool is provided by the KIS MCP Server MCP server (soyjefu/kis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.