AI agents call openapi_server_info to retrieve information from Openapi Mcp Sdk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The naming convention (openapi_server_info) and the context of sibling tools (check_*) that retrieve data without modification suggest this retrieves metadata or status information about the API server itself. This is a passive information lookup with no side effects. Lack of description reduces confidence slightly, but the pattern and server purpose point clearly to a Read operation.
From the tool's definition Tool name 'openapi_server_info' suggests querying server information; description is empty, which lowers confidence. The server's stated purpose is 'retrieve official documents and data,' indicating primarily read operations.
Documented attack patterns abuse exactly the kind of access openapi_server_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Openapi Mcp Sdk, and nothing reaches the server without passing your rules. This is the rule we recommend for openapi_server_info:
{
"version": "1",
"default": "deny",
"tools": {
"openapi_server_info": {}
}
}openapi_server_info 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.
openapi_server_info. It is categorised as a Read tool in the Openapi Mcp Sdk MCP Server, which means it retrieves data without modifying state.
Register the Openapi Mcp Sdk MCP server in PolicyLayer and add a rule for openapi_server_info: 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 Openapi Mcp Sdk. Nothing to install.
openapi_server_info 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 openapi_server_info 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 openapi_server_info. 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.
openapi_server_info is provided by the Openapi Mcp Sdk MCP server (openapi/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Openapi Mcp Sdk, 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.
41 Openapi Mcp Sdk tools catalogued and risk-classified — across an index of 43,000+ MCP servers.