Low Risk

list_all_endpoints

列出所有接口的路径和方法(仅返回摘要信息)

How to control list_all_endpoints ↓

What list_all_endpoints does on Apifox Filter MCP Server

AI agents call list_all_endpoints to retrieve information from Apifox Filter MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_all_endpoints needs a policy

This tool retrieves and lists API endpoint metadata (paths and methods) without modifying, executing, deleting, or creating any resources. It is a query/list operation with no side effects, fitting the Read category. The 'summary information only' qualifier confirms it returns limited reference data rather than triggering operations.

From the tool's definition Tool name 'list_all_endpoints' and description 'list all endpoints' (translated from Chinese: '列出所有接口的路径和方法(仅返回摘要信息)' = 'list all interface paths and methods (only return summary information)') indicates data retrieval with no modification.

Documented attack patterns abuse exactly the kind of access list_all_endpoints gives an agent:

How to control list_all_endpoints

PolicyLayer is an MCP gateway — it sits between your AI agents and Apifox Filter MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_all_endpoints:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_all_endpoints": {}
  }
}

list_all_endpoints is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Apifox Filter MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_all_endpoints

What does the list_all_endpoints tool do? +

列出所有接口的路径和方法(仅返回摘要信息). It is categorised as a Read tool in the Apifox Filter MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_all_endpoints? +

Register the Apifox Filter MCP Server MCP server in PolicyLayer and add a rule for list_all_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 Filter MCP Server. Nothing to install.

What risk level is list_all_endpoints? +

list_all_endpoints is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_all_endpoints? +

Yes. Add a rate_limit block to the list_all_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.

How do I block list_all_endpoints completely? +

Set action: deny in the PolicyLayer policy for list_all_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.

What MCP server provides list_all_endpoints? +

list_all_endpoints is provided by the Apifox Filter MCP Server MCP server (xiaou66/apifox-filter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Apifox Filter MCP Server tool call.

Start from Apifox Filter 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.

9 Apifox Filter MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.