Get full details of a single API interface, including all parameter definitions and response examples. Parameters: - source (required): Service name, from the [service name] returned by swagger_list_sources or swagger_search_api. - method (required): HTTP method, e.g.
AI agents call swagger_get_api_detail to retrieve information from Internal Swagger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing API documentation metadata. It performs a read-only lookup operation with no side effects on the underlying systems or data. The parameters (source, method) are used only to filter and fetch documentation, not to execute code or modify state. Risk is minimal since it only exposes documentation that should already be intended for consumption.
From the tool's definition Tool retrieves API documentation details with 'Get full details of a single API interface, including all parameter definitions and response examples.' No mutation, deletion, or execution capability.
Attacks that exploit this kind of access
Get full details of a single API interface, including all parameter definitions and response examples. Parameters: - source (required): Service name, from the [service name] returned by swagger_list_sources or swagger_search_api. - method (required): HTTP method, e.g. It is categorised as a Read tool in the Internal Swagger MCP Server, which means it retrieves data without modifying state.
Register the Internal Swagger MCP server in PolicyLayer and add a rule for swagger_get_api_detail: 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 Internal Swagger. Nothing to install.
swagger_get_api_detail 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 swagger_get_api_detail 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 swagger_get_api_detail. 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.
swagger_get_api_detail is provided by the Internal Swagger MCP server (zhangwanli09/internal-swagger-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 →