AI agents call search_api to retrieve information from ZStack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches or indexes ZStack Cloud APIs (2000+ available), enabling discovery of what operations are available. Search operations are Read category as they retrieve information without side effects.
From the tool's definition Tool name 'search_api' indicates information retrieval/discovery of available APIs. Server description mentions 'dynamically search' APIs as a core function.
Documented attack patterns abuse exactly the kind of access search_api gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZStack MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_api:
{
"version": "1",
"default": "deny",
"tools": {
"search_api": {}
}
}search_api 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.
search_api. It is categorised as a Read tool in the ZStack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ZStack MCP Server MCP server in PolicyLayer and add a rule for search_api: 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 ZStack MCP Server. Nothing to install.
search_api 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_api 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_api. 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_api is provided by the ZStack MCP Server MCP server (zstackio/zstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ZStack MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 ZStack MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.