列出所有可用的 Swagger 檔案
AI agents call list_swaggers to retrieve information from Swagger Json without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists metadata about available Swagger/OpenAPI documentation files. It performs a query-like operation that returns information without modifying, deleting, or executing anything. The blast radius is minimal—misuse would only expose what Swagger files exist in the system, which is non-destructive read-only information access.
From the tool's definition Tool name 'list_swaggers' and description '列出所有可用的 Swagger 檔案' (list all available Swagger files) indicate a retrieval/listing operation with no side effects.
Attacks that exploit this kind of access
列出所有可用的 Swagger 檔案. It is categorised as a Read tool in the Swagger Json MCP Server, which means it retrieves data without modifying state.
Register the Swagger Json MCP server in PolicyLayer and add a rule for list_swaggers: 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 Swagger Json. Nothing to install.
list_swaggers 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 list_swaggers 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 list_swaggers. 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.
list_swaggers is provided by the Swagger Json MCP server (llm-mcp-servers/swagger-json-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 →