openapi_get_response_codes
A read tool on the MCP Framework Personal MCP server.
This record as markdown: /tools/inggerman-mcps/openapi-get-response-codes.md
What openapi_get_response_codes does on MCP Framework Personal
AI agents call openapi_get_response_codes to retrieve information from MCP Framework Personal without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why openapi_get_response_codes is rated Low
The tool appears to retrieve or query response code metadata from OpenAPI schemas, which is a read-only operation with no side effects. While the empty description reduces confidence slightly, the function name strongly suggests introspection/retrieval of API documentation data rather than execution, modification, or deletion. Blast radius is minimal as it only returns information.
From the tool's definition Tool name 'openapi_get_response_codes' indicates retrieval of HTTP response code information from an OpenAPI specification. No description provided, but the naming pattern suggests a query/lookup operation rather than modification or execution.
Attacks that exploit this kind of access
The rule that runs openapi_get_response_codes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Framework Personal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openapi_get_response_codes, this is the rule to start with:
openapi_get_response_codes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Framework Personal, apply this rule, and every openapi_get_response_codes call is checked against it from then on.
Questions about openapi_get_response_codes
openapi_get_response_codes is a read tool on the MCP Framework Personal MCP server. It is categorised as a Read tool in the MCP Framework Personal MCP Server, which means it retrieves data without modifying state.
Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for openapi_get_response_codes: 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 MCP Framework Personal. Nothing to install.
openapi_get_response_codes 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_get_response_codes 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_get_response_codes. 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_get_response_codes is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Framework Personal, and thousands of servers like it.
This server
Across the catalogue