Low Risk

get_alpha_signals

get_alpha_signals

How to control get_alpha_signals ↓

What get_alpha_signals does on Momentum

AI agents call get_alpha_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.

Low Risk

Why get_alpha_signals needs a policy

Alpha signals are typically computed metrics or indicators retrieved for analysis. The tool appears designed to query or fetch pre-calculated trading signals rather than execute trades, modify accounts, or delete data.

From the tool's definition Tool name 'get_alpha_signals' and server context (quantitative trading analysis) suggest retrieval of trading signals or metrics.

Documented attack patterns abuse exactly the kind of access get_alpha_signals gives an agent:

How to control get_alpha_signals

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_alpha_signals:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_alpha_signals": {}
  }
}

get_alpha_signals is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Momentum — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_alpha_signals

What does the get_alpha_signals tool do? +

get_alpha_signals. It is categorised as a Read tool in the Momentum MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_alpha_signals? +

Register the Momentum MCP server in PolicyLayer and add a rule for get_alpha_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.

What risk level is get_alpha_signals? +

get_alpha_signals is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_alpha_signals? +

Yes. Add a rate_limit block to the get_alpha_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.

How do I block get_alpha_signals completely? +

Set action: deny in the PolicyLayer policy for get_alpha_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.

What MCP server provides get_alpha_signals? +

get_alpha_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.

Enforce policy on every Momentum tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.