AI agents call list_api_endpoints to retrieve information from Apifox MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and enumerates existing API endpoints without modifying, executing, or deleting any data. It is a read-only operation that queries the state of the system. The severity is low because exposing a list of API endpoints poses minimal risk; it is informational data about the system structure.
From the tool's definition Tool name is 'list_api_endpoints' and description states it lists ('列出') all HTTP interfaces in an Apifox project. This is a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_api_endpoints gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apifox MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_api_endpoints:
{
"version": "1",
"default": "deny",
"tools": {
"list_api_endpoints": {}
}
}list_api_endpoints is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
列出 Apifox 项目中的所有 HTTP 接口。. It is categorised as a Read tool in the Apifox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Apifox MCP Server 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 Apifox MCP Server. 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 Apifox MCP Server MCP server (iwen-conf/apifox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apifox MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 Apifox MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.