Find tools matching a pattern in a specific MCP server (returns name and description only)
AI agents call find-tools-in-server to retrieve information from MCP Hub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search/discovery operation that retrieves metadata (tool names and descriptions) from a server without modifying, executing, or deleting anything. It is read-only information retrieval, presenting minimal security risk even if invoked by an agent. Severity is low because the blast radius is limited to disclosure of tool availability and documentation.
From the tool's definition Tool description states it 'Find tools matching a pattern in a specific MCP server (returns name and description only)' — a pure query/search operation with no side effects.
Documented attack patterns abuse exactly the kind of access find-tools-in-server gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Hub MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for find-tools-in-server:
{
"version": "1",
"default": "deny",
"tools": {
"find-tools-in-server": {}
}
}find-tools-in-server is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find tools matching a pattern in a specific MCP server (returns name and description only). It is categorised as a Read tool in the MCP Hub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Hub MCP Server MCP server in PolicyLayer and add a rule for find-tools-in-server: 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 MCP Hub MCP Server. Nothing to install.
find-tools-in-server is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the find-tools-in-server 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.
Set action: deny in the PolicyLayer policy for find-tools-in-server. 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.
find-tools-in-server is provided by the MCP Hub MCP Server MCP server (warpdev/mcp-hub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 MCP Hub MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 MCP Hub MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.