Detect market topping signals using distribution days and leadership trends.
AI agents call detect_market_top 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 retrieves and analyzes existing market data (distribution days, leadership trends) to generate signals. It is purely analytical with no side effects, reversible operations, code execution, data destruction, or financial commitments. It fits the 'Read' category as it queries and analyzes data without modifying any state.
From the tool's definition Tool name 'detect_market_top' and description 'Detect market topping signals using distribution days and leadership trends' indicate analysis and signal detection. No modification, deletion, execution of external commands, or financial transactions occur.
Documented attack patterns abuse exactly the kind of access detect_market_top 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 detect_market_top:
{
"version": "1",
"default": "deny",
"tools": {
"detect_market_top": {}
}
}detect_market_top 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.
Detect market topping signals using distribution days and leadership trends. 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 detect_market_top: 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.
detect_market_top 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 detect_market_top 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 detect_market_top. 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.
detect_market_top 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.