AI agents call list_api_folders 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.
This tool retrieves and displays the hierarchical structure of API folders in Apifox. It performs a query operation with no side effects—it does not create, modify, execute, delete, or commit financial actions. The blast radius of misuse is minimal; an agent could at worst enumerate the folder structure to understand available APIs, but cannot take any destructive or sensitive actions.
From the tool's definition Tool name 'list_api_folders' and description '列出所有 Apifox 接口文件夹目录结构' (list all Apifox API folder directory structure) indicates retrieval of folder/directory metadata with no modification or execution.
Documented attack patterns abuse exactly the kind of access list_api_folders gives an agent:
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_api_folders:
{
"version": "1",
"default": "deny",
"tools": {
"list_api_folders": {}
}
}list_api_folders 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 接口文件夹目录结构. It is categorised as a Read tool in the Apifox Filter MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Apifox Filter MCP Server MCP server in PolicyLayer and add a rule for list_api_folders: 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.
list_api_folders 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_folders 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_folders. 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_folders 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.
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.