Breakout and continuation signals with technical indicator data.
AI agents call get_signals 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 aggregates technical analysis signals derived from market data. It is a pure read operation that analyzes and returns information without modifying state, executing commands, or committing financial actions.
From the tool's definition Tool name 'get_signals' and description 'Breakout and continuation signals with technical indicator data' indicate data retrieval and analysis. No mention of execution, modification, deletion, or financial transactions.
Documented attack patterns abuse exactly the kind of access get_signals 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 get_signals:
{
"version": "1",
"default": "deny",
"tools": {
"get_signals": {}
}
}get_signals 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.
Breakout and continuation signals with technical indicator data. 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 get_signals: 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.
get_signals 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 get_signals 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 get_signals. 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.
get_signals 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.