Identify trending market themes by clustering thematic ETF performance.
AI agents call detect_themes 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 ETF performance data to identify patterns, similar to other analytical tools on the server (analyze_technicals, analyze_breadth). It reads market information and performs statistical clustering, which are read-only operations with no side effects. No data is modified, deleted, or financial transactions are initiated.
From the tool's definition Tool performs 'clustering thematic ETF performance' and 'identify trending market themes'—both passive data analysis operations that retrieve and categorize existing market data without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access detect_themes 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_themes:
{
"version": "1",
"default": "deny",
"tools": {
"detect_themes": {}
}
}detect_themes 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.
Identify trending market themes by clustering thematic ETF performance. 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_themes: 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_themes 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_themes 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_themes. 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_themes 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.