AI agents call list_endpoints to retrieve information from Mcp Docs 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 structured data (API endpoint definitions) from bundled OpenAPI documentation. It performs no modifications, deletions, or external operations—it is purely informational retrieval. The severity is low because misuse would at worst leak documentation structure, not cause data loss or execute unintended operations.
From the tool's definition Tool description states 'List ProsodyAI REST API endpoints from the bundled OpenAPI spec' with optional filters. The verb 'list' and the action of retrieving/querying endpoint metadata from documentation has no side effects.
Attacks that exploit this kind of access
List ProsodyAI REST API endpoints from the bundled OpenAPI spec. Optional filters by tag or path substring. It is categorised as a Read tool in the Mcp Docs MCP Server, which means it retrieves data without modifying state.
Register the Mcp Docs MCP server in PolicyLayer and add a rule for list_endpoints: 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 Docs. Nothing to install.
list_endpoints 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_endpoints 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_endpoints. 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_endpoints is provided by the Mcp Docs MCP server (prosodyai/mcp-docs). 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 →