Searches for relevant tools based on a task description.
AI agents call search_tools to retrieve information from UTCP-MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information from the UTCP tool registry to help users find relevant tools. It is purely informational—it queries existing data without creating, modifying, deleting, or executing anything. This is a classic Read category operation similar to search, list, or get functions. The severity is low because misuse (e.g., searching for tools repeatedly) poses minimal risk.
From the tool's definition The tool 'search_tools' is described as performing a search operation based on a task description. The verb 'searches' and the function of retrieving relevant tools from a registry indicate a query/retrieval operation with no modification of data or side…
Documented attack patterns abuse exactly the kind of access search_tools gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and UTCP-MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for search_tools:
{
"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.
Free to start. No card required.
Searches for relevant tools based on a task description. It is categorised as a Read tool in the UTCP-MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the UTCP-MCP Bridge 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 UTCP-MCP Bridge. Nothing to install.
search_tools 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 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.
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.
search_tools is provided by the UTCP-MCP Bridge MCP server (universal-tool-calling-protocol/utcp-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 UTCP-MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 UTCP-MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.