Create and backtest a strategy ensemble across multiple symbols. Args: symbols: List of stock symbols base_strategies: List of base strategy names to ensemble weighting_method: Weighting method (performance, equal, volatility) start_date: Start date for backtesting end_date: End date for backtest...
AI agents invoke create_strategy_ensemble 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 tool executes a backtesting simulation (running computational strategies against historical data) rather than simply reading data or modifying stored records. It performs analysis/computation with side effects in the form of derived results, but does not move money, delete data, or irreversibly modify anything.
From the tool's definition 'Create and backtest a strategy ensemble across multiple symbols' — runs a backtesting simulation using historical data and computes strategy weights
Documented attack patterns abuse exactly the kind of access create_strategy_ensemble 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 create_strategy_ensemble:
{
"version": "1",
"default": "deny",
"tools": {
"create_strategy_ensemble": {
"limits": [
{
"counter": "create_strategy_ensemble_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}create_strategy_ensemble 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.
Create and backtest a strategy ensemble across multiple symbols. Args: symbols: List of stock symbols base_strategies: List of base strategy names to ensemble weighting_method: Weighting method (performance, equal, volatility) start_date: Start date for backtesting end_date: End date for backtesting initial_capital: Initial capital per symbol Returns: Ensemble backtest results with strategy weights. 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 create_strategy_ensemble: 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.
create_strategy_ensemble 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 create_strategy_ensemble 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 create_strategy_ensemble. 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.
create_strategy_ensemble 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.