AI agents invoke run_stock_screen to trigger actions in Momentum. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The name suggests executing a stock screening operation, which likely queries market data and applies filters/criteria to identify stocks. Given the server context (quantitative trading, technical indicators), this tool probably runs a screen/scan against market data. However, the empty description significantly lowers confidence.
From the tool's definition Tool name 'run_stock_screen' on a quantitative trading analysis server; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access run_stock_screen 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 run_stock_screen:
{
"version": "1",
"default": "deny",
"tools": {
"run_stock_screen": {
"limits": [
{
"counter": "run_stock_screen_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_stock_screen stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
run_stock_screen. It is categorised as a Execute tool in the Momentum MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Momentum MCP server in PolicyLayer and add a rule for run_stock_screen: 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.
run_stock_screen is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_stock_screen 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 run_stock_screen. 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.
run_stock_screen 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.