search_tools

THE RISK

Low Risk

Why search_tools needs a policy

This tool performs a query operation that searches and retrieves information from a verified index. It has no side effects, does not execute code, does not modify data, and does not delete or move resources. The semantic search mechanism allows AI agents to discover verified CLI tools reliably, reducing hallucination. Misuse would be limited to information gathering with minimal blast radius.

From the tool's definition Tool description explicitly states 'Semantic search across 10,000+ verified CLI tools' — a retrieval operation with no modification or execution capability.

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

POLICY

How to control search_tools

PolicyLayer is an MCP gateway — it sits between your AI agents and Need, and nothing reaches the server without passing your rules. This is the rule we recommend for search_tools:

policy.json

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

search_tools 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 Need — 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 Need tools

Execute install_tool Install a CLI tool by name using an allowlisted package manager (brew, apt, npm, pip, carg Write report_tool_usage Report whether a tool worked or failed. Improves future search rankings for all agents.

All 3 Need 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 search_tools

What does the search_tools tool do? +

Semantic search across 10,000+ verified CLI tools. Describe what you need in plain English. It is categorised as a Read tool in the Need MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_tools? +

Register the Need MCP server in PolicyLayer and add a rule for search_tools: 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 Need. Nothing to install.

What risk level is search_tools? +

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

Can I rate-limit search_tools? +

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

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

search_tools is provided by the Need MCP server (tuckerschreiber/need). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Need tool call.

Start from Need, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →