AI agents call search_api to retrieve information from Openstudio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the naming convention and context of the OpenStudio MCP server (which supports querying models and analyzing results), 'search_api' most likely retrieves or queries data without side effects. The empty description reduces confidence, but the name pattern is consistent with Read operations.
From the tool's definition Tool name 'search_api' suggests information retrieval or querying functionality. No description provided to confirm.
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 Openstudio, 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 Openstudio MCP Server, which means it retrieves data without modifying state.
Register the Openstudio 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 Openstudio. 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 Openstudio MCP server (natlabrockies/openstudio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Openstudio, 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.
146 Openstudio tools catalogued and risk-classified — across an index of 43,000+ MCP servers.