Compute statistical price targets using historical volatility.
AI agents call model_price_distribution to retrieve information from Momentum without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool analyzes existing financial data to generate statistical projections, which is characteristic of Read operations. It retrieves and processes historical information to produce insights, but does not create, modify, delete, or execute external operations. The context of a quantitative trading analysis server confirms this is analytical research rather than transaction execution or order placement.
From the tool's definition Tool computes statistical price targets using historical volatility data—a read-only analytical operation.
Documented attack patterns abuse exactly the kind of access model_price_distribution gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Momentum, and nothing reaches the server without passing your rules. This is the rule we recommend for model_price_distribution:
{
"version": "1",
"default": "deny",
"tools": {
"model_price_distribution": {}
}
}model_price_distribution is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Compute statistical price targets using historical volatility. It is categorised as a Read tool in the Momentum MCP Server, which means it retrieves data without modifying state.
Register the Momentum MCP server in PolicyLayer and add a rule for model_price_distribution: 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 Momentum. Nothing to install.
model_price_distribution 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 model_price_distribution 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 model_price_distribution. 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.
model_price_distribution is provided by the Momentum MCP server (mphinance/momentum-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Momentum, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
52 Momentum tools catalogued and risk-classified — across an index of 43,000+ MCP servers.