search

Searches the npm registry for packages matching a query.

SERVERGit SOURCEDave-London/Pare

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-git/search.md

WHAT IT DOES

What search does on Git

AI agents call search to retrieve information from Git without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why search is rated Low

This tool retrieves information from an external registry (npm) without modifying any data, creating resources, executing code, or causing irreversible changes. It is a pure read operation. The low severity reflects the minimal risk: even if an AI agent misuses this tool, the worst outcome is querying for unintended packages, which has no blast radius.

From the tool's definition Tool name 'search' combined with description 'Searches the npm registry for packages matching a query' indicates a query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Git, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search, this is the rule to start with:

search Allowed

search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Git, apply this rule, and every search call is checked against it from then on.

FAQ

Questions about search

What does the search tool do? +

Searches the npm registry for packages matching a query. It is categorised as a Read tool in the Git MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search? +

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

What risk level is search? +

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

Can I rate-limit search? +

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

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

search is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Git, and thousands of servers like it.

This server

All 202 Git tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →