mcp_registry_search

Search the MCP server registry by keyword

SERVERMeta Data Mcp SOURCEpypi:meta-data-mcp

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-derekslinz-meta-data-mcp/mcp-registry-search.md

WHAT IT DOES

What mcp_registry_search does on Meta Data Mcp

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

RISK

Why mcp_registry_search is rated Low

This tool performs a read-only search against a registry. It queries data and returns results without creating, modifying, deleting, or executing any actions. The keyword search pattern is characteristic of retrieval operations with no blast radius for misuse—it simply returns matching registry entries.

From the tool's definition Tool name 'mcp_registry_search' and description 'Search the MCP server registry by keyword' indicate a query operation that retrieves information without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mcp_registry_search safely

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

mcp_registry_search Allowed

mcp_registry_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": {
    "mcp_registry_search": {}
  }
}

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

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

FAQ

Questions about mcp_registry_search

What does the mcp_registry_search tool do? +

Search the MCP server registry by keyword. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mcp_registry_search? +

Register the Meta Data MCP server in PolicyLayer and add a rule for mcp_registry_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 Meta Data Mcp. Nothing to install.

What risk level is mcp_registry_search? +

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

Can I rate-limit mcp_registry_search? +

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

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

mcp_registry_search is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meta Data, and thousands of servers like it.

This server

All 396 Meta Data 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 →