list_strategies

THE RISK

Low Risk

Why list_strategies needs a policy

This tool retrieves or queries existing strategy data without side effects. It performs a simple listing operation typical of Read category tools. The lack of any creation, modification, deletion, execution, or financial transaction language confirms this is a non-destructive information retrieval function.

From the tool's definition Tool name 'list_strategies' and description 'List all saved custom strategies' indicate a retrieval operation with no modification or execution of data.

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

POLICY

How to control list_strategies

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_strategies": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Momentum tools

Financial find_best_to_sell Auto-find the best puts and calls to SELL. Scans 7-45 DTE across Execute run_custom_screen run_custom_screen Execute run_stock_screen run_stock_screen Execute sweep_strategy Run a strategy across multiple tickers (max 20). Ranks by Sharpe/return. Execute backtest_strategy Backtest a trading strategy on historical data. 6 presets: Execute walk_forward_test Walk-forward validation: splits data into n folds, detects overfitting. Write log_conviction Log a trade conviction to the journal. Direction: long/short. Write save_strategy Save a custom strategy to disk for re-use.

All 52 Momentum tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_strategies

What does the list_strategies tool do? +

List all saved custom strategies. 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 list_strategies? +

Register the Momentum MCP server in PolicyLayer and add a rule for list_strategies: 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 list_strategies? +

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

Can I rate-limit list_strategies? +

Yes. Add a rate_limit block to the list_strategies 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 list_strategies completely? +

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

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

CHECK YOUR STACK →