get_backtest_result_tool
AI agents call get_backtest_result_tool to retrieve information from KIS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix strongly suggests a read operation that retrieves previously computed backtest results. In the context of a financial trading platform, backtest results are historical data outputs without side effects. However, confidence is reduced due to the empty description, and severity is medium (not low) because the tool operates in a financial domain where misuse could inform poor trading decisions.
From the tool's definition Tool name contains 'get_' and 'backtest_result', indicating data retrieval. Description is empty, limiting confidence.
Attacks that exploit this kind of access
get_backtest_result_tool. It is categorised as a Read tool in the KIS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the KIS MCP Server MCP server in PolicyLayer and add a rule for get_backtest_result_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.
get_backtest_result_tool is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_backtest_result_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.
Set action: deny in the PolicyLayer policy for get_backtest_result_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.
get_backtest_result_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →