Train an ML predictor model for trading signals. Args: symbol: Stock symbol to train on start_date: Start date for training data end_date: End date for training data model_type: ML model type (random_forest) target_periods: Forward periods for target variable return_threshold: Return threshold fo...
AI agents invoke train_ml_predictor 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 code that trains machine learning models and generates trading signals, which are predictive operations with external effects (the trained model informs trading decisions). While the tool itself doesn't directly execute trades, it generates the signals that would drive trading actions, making it an Execute operation rather than Read.
From the tool's definition Tool trains an ML predictor model with configurable parameters (model_type, n_estimators, max_depth, min_samples_split) and executes model training operations.
Documented attack patterns abuse exactly the kind of access train_ml_predictor 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 train_ml_predictor:
{
"version": "1",
"default": "deny",
"tools": {
"train_ml_predictor": {
"limits": [
{
"counter": "train_ml_predictor_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}train_ml_predictor 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.
Train an ML predictor model for trading signals. Args: symbol: Stock symbol to train on start_date: Start date for training data end_date: End date for training data model_type: ML model type (random_forest) target_periods: Forward periods for target variable return_threshold: Return threshold for signal classification n_estimators, max_depth, min_samples_split: Model-specific parameters Returns: Training results and model metrics. 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 train_ml_predictor: 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.
train_ml_predictor 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 train_ml_predictor 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 train_ml_predictor. 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.
train_ml_predictor 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.