retry_backtest_tool · KIS MCP Server MCP: Risk & Policy

WHAT IT DOES

What retry_backtest_tool does on KIS MCP Server

AI agents invoke retry_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 retry_backtest_tool needs a policy

The tool name implies re-running a previously failed or incomplete backtest operation. Based on sibling tools that explicitly run backtests, this tool likely triggers execution of backtesting logic. Backtesting simulates trading strategies on historical data without actual financial transactions, making it Execute category. Confidence is low due to empty description.

From the tool's definition Tool name 'retry_backtest_tool' and sibling tools 'run_backtest_tool', 'run_batch_backtest_tool', 'run_preset_backtest_tool' suggest this retries a backtest execution

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

retry_backtest_tool Rate-limited

retry_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": {
    "retry_backtest_tool": {
      "limits": [
        {
          "counter": "retry_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 retry_backtest_tool

What does the retry_backtest_tool tool do? +

retry_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 retry_backtest_tool? +

Register the KIS MCP Server MCP server in PolicyLayer and add a rule for retry_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 retry_backtest_tool? +

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

Can I rate-limit retry_backtest_tool? +

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

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

retry_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.