Compare multiple strategies on the same symbol. Args: symbol: Stock symbol strategies: List of strategy types to compare (defaults to all) start_date: Start date (YYYY-MM-DD) end_date: End date (YYYY-MM-DD) Returns: Comparison results with rankings and analysis
AI agents invoke compare_strategies to trigger actions in MaverickMCP. 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.
This is Execute rather than Read because it runs multi-strategy comparative analysis and generates rankings/analysis results based on parametric inputs. While not modifying real financial positions or data, it executes computational financial operations that could lead an AI agent to make harmful trading decisions if the strategy parameters or date ranges are maliciously chosen.
From the tool's definition The tool compares multiple strategies on stock symbols using historical data ranges (start_date, end_date).
Documented attack patterns abuse exactly the kind of access compare_strategies gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MaverickMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for compare_strategies:
{
"version": "1",
"default": "deny",
"tools": {
"compare_strategies": {
"limits": [
{
"counter": "compare_strategies_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} compare_strategies 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.
Free to start. No card required.
Compare multiple strategies on the same symbol. Args: symbol: Stock symbol strategies: List of strategy types to compare (defaults to all) start_date: Start date (YYYY-MM-DD) end_date: End date (YYYY-MM-DD) Returns: Comparison results with rankings and analysis. It is categorised as a Execute tool in the MaverickMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Maverick MCP server in PolicyLayer and add a rule for compare_strategies: 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 MaverickMCP. Nothing to install.
compare_strategies is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the compare_strategies 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_strategies. 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_strategies is provided by the Maverick MCP server (wshobson/maverick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 54 MaverickMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
54 MaverickMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.