List all available API endpoints
AI agents call list-api-endpoints to retrieve information from Openapi Mcp Server Fork without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and lists metadata about available API endpoints without modifying, deleting, or executing any operations. It performs passive discovery only. Low severity because disclosure of endpoint names poses minimal risk on its own; an attacker would still need to invoke endpoints via the 'invoke-api-endpoint' tool to cause harm.
From the tool's definition Tool name is 'list-api-endpoints' and description states 'List all available API endpoints' — this is a query/enumeration operation with no side effects.
Attacks that exploit this kind of access
List all available API endpoints. It is categorised as a Read tool in the Openapi Mcp Server Fork MCP Server, which means it retrieves data without modifying state.
Register the Openapi Mcp Server Fork MCP server in PolicyLayer and add a rule for list-api-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 Openapi Mcp Server Fork. Nothing to install.
list-api-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-api-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-api-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-api-endpoints is provided by the Openapi Mcp Server Fork MCP server (@shyrogan/openapi-mcp-server-fork). 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 →