List all configured Swagger documentation sources and their cache status. For each service, returns: - name: Service name (from config, or auto-read from projectName). - fetchedAt: Last cache time (null means not yet loaded). - totalInterfaces: Total interface count (shown when loaded). - modules...
AI agents call swagger_list_sources 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 retrieves and queries configuration and cache status information without side effects. It is a pure read operation that discovers available API documentation sources. The blast radius is minimal—exposure merely reveals which APIs are documented and their cache state, posing no direct risk to data or systems.
From the tool's definition Tool returns metadata about configured Swagger documentation sources: 'name', 'fetchedAt', 'totalInterfaces', 'modules'.
Attacks that exploit this kind of access
List all configured Swagger documentation sources and their cache status. For each service, returns: - name: Service name (from config, or auto-read from projectName). - fetchedAt: Last cache time (null means not yet loaded). - totalInterfaces: Total interface count (shown when loaded). - modules: Module list. Use this before calling swagger_search_api to discover which services are available. 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_list_sources: 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_list_sources 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_list_sources 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_list_sources. 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_list_sources 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 →