Compare strategy performance between Conservative (T+1 Open entry) and Aggressive (same-day Close entry) timing modes. Shows side-by-side comparison with delta calculations for each metric.
AI agents call compare_timing_modes to retrieve information from Mcp Strategy Research Db without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a SQLite database to retrieve and compare strategy performance data across different timing modes. It is purely analytical—it reads historical backtest results and computes comparative metrics (deltas). No data is created, modified, deleted, or executed. The description uses passive language ('Shows', 'Compare') indicating data retrieval only.
From the tool's definition Tool performs 'side-by-side comparison with delta calculations' on existing backtest results, retrieving and analyzing strategy performance metrics without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Compare strategy performance between Conservative (T+1 Open entry) and Aggressive (same-day Close entry) timing modes. Shows side-by-side comparison with delta calculations for each metric. It is categorised as a Read tool in the Mcp Strategy Research Db MCP Server, which means it retrieves data without modifying state.
Register the Mcp Strategy Research Db MCP server in PolicyLayer and add a rule for compare_timing_modes: 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 Mcp Strategy Research Db. Nothing to install.
compare_timing_modes 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 compare_timing_modes 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 compare_timing_modes. 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.
compare_timing_modes is provided by the Mcp Strategy Research Db MCP server (locupleto/mcp-strategy-research-db). 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 →