Get detailed information about a specific API endpoint
AI agents call swagger_get_endpoint_details to retrieve information from Multi-Database MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries API endpoint documentation/metadata from a Swagger/OpenAPI specification. It has no side effects, does not execute code or commands, and does not modify any data. It is a read-only information retrieval operation, fitting the 'Read' category for tools that retrieve or query data without side effects.
From the tool's definition Tool name 'swagger_get_endpoint_details' and description 'Get detailed information about a specific API endpoint' indicate retrieval of metadata/documentation about API endpoints with no modification or execution of endpoints themselves.
Attacks that exploit this kind of access
Get detailed information about a specific API endpoint. It is categorised as a Read tool in the Multi-Database MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Multi-Database MCP Server MCP server in PolicyLayer and add a rule for swagger_get_endpoint_details: 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 Multi-Database MCP Server. Nothing to install.
swagger_get_endpoint_details 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_endpoint_details 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_endpoint_details. 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_endpoint_details is provided by the Multi-Database MCP Server MCP server (nam088/mcp-server). 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 →