Search the deferred schema-editing tool catalog — ztype editing tools not resident by default (third-party API/TPA config CRUD, ZAI config, etc.). Returns the top matches with full arg schemas inline, plus a brief list of further matches. Execute a found tool through the resident ztype_tool_calls...
AI agents call search_tools to retrieve information from Zion without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | |
query | string | Yes |
Parameters from the server's own tool schema.
This is a search/query tool that retrieves information about available tools from a catalog. It has no side effects—it does not create, modify, delete, or execute anything. It purely retrieves and presents matching tool metadata and schemas. This fits the Read category (retrieves or queries data; no side effects).
From the tool's definition Tool description states it 'Search[es] the deferred schema-editing tool catalog' and 'Returns the top matches with full arg schemas inline, plus a brief list of further matches.' The verb 'search' and 'returns' indicate data retrieval with no modification.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Search the deferred schema-editing tool catalog — ztype editing tools not resident by default (third-party API/TPA config CRUD, ZAI config, etc.). Returns the top matches with full arg schemas inline, plus a brief list of further matches. Execute a found tool through the resident ztype_tool_calls tool. Query forms: plain keywords ("tpa response data"); "+token" requires the token in the tool name; "select:name1,name2" returns those tools directly. It is categorised as a Read tool in the Zion MCP Server, which means it retrieves data without modifying state.
search_tools accepts 2 parameters: limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Zion 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 Zion. 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 Zion MCP server (zion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →