Critical Risk →

delete_folder

删除 Apifox 项目中的目录(标签)。⚠️ 警告: 此操作不可撤销!

How to control delete_folder ↓

What delete_folder does on Apifox MCP Server

AI agents call delete_folder to permanently remove resources in Apifox MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_folder needs a policy

This tool irreversibly deletes folders/directories from an API management system. The explicit warning that the operation cannot be undone (不可撤销) clearly indicates data loss. Even though it targets folder structure rather than individual data records, the destructive nature and unrecoverable outcome make this critical for security classification.

From the tool's definition The tool description explicitly states '删除 Apifox 项目中的目录' (delete folder from Apifox project) and includes a warning '⚠️ 警告: 此操作不可撤销!' (Warning: This operation cannot be undone!).

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

How to control delete_folder

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 delete_folder:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_folder"
  ]
}

delete_folder disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Apifox 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.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_folder

What does the delete_folder tool do? +

删除 Apifox 项目中的目录(标签)。⚠️ 警告: 此操作不可撤销!. It is categorised as a Destructive tool in the Apifox MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_folder? +

Register the Apifox MCP Server MCP server in PolicyLayer and add a rule for delete_folder: 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.

What risk level is delete_folder? +

delete_folder is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_folder? +

Yes. Add a rate_limit block to the delete_folder 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 delete_folder completely? +

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

delete_folder 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.

Enforce policy on every Apifox MCP Server tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.