Low Risk

pfdf_search_firms

Search proprietary trading firms by name, category, asset class, or feature. Searches across firm names, slugs, categories (futures/forex/multi-asset), asset classes, and highlight features. Returns matching firms with full details and discount codes. Args: - query (string): Search term (e.g....

Accepts freeform code/query input (query); Single-target operation

Part of the Prop Firm Deal Finder MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call pfdf_search_firms to retrieve information from Prop Firm Deal Finder without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though pfdf_search_firms only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

prop-firm-deal-finder.yaml
tools:
  pfdf_search_firms:
    rules:
      - action: allow

See the full Prop Firm Deal Finder policy for all 6 tools.

Tool Name pfdf_search_firms
Category Read
Risk Level Low

Agents calling read-class tools like pfdf_search_firms have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the pfdf_search_firms tool do? +

Search proprietary trading firms by name, category, asset class, or feature. Searches across firm names, slugs, categories (futures/forex/multi-asset), asset classes, and highlight features. Returns matching firms with full details and discount codes. Args: - query (string): Search term (e.g., 'FTMO', 'futures', 'instant funding', 'crypto') Returns: Markdown-formatted list of matching firms with details and discount codes. Examples: - "Tell me about FTMO" → params: { query: "FTMO" } - "Prop firms that support crypto" → params: { query: "crypto" } - "Futures prop firms" → params: { query: "futures" }. It is categorised as a Read tool in the Prop Firm Deal Finder MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pfdf_search_firms? +

Add a rule in your Intercept YAML policy under the tools section for pfdf_search_firms. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Prop Firm Deal Finder MCP server.

What risk level is pfdf_search_firms? +

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

Can I rate-limit pfdf_search_firms? +

Yes. Add a rate_limit block to the pfdf_search_firms rule in your Intercept 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 pfdf_search_firms completely? +

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

pfdf_search_firms is provided by the Prop Firm Deal Finder MCP server (propfirmdealfinder-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Prop Firm Deal Finder

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.