AI agents call delete_api_endpoint 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.
This tool permanently removes API endpoint definitions from an Apifox project with no undo capability. Deletion of API endpoints could disrupt API documentation, testing, and integration workflows. An AI agent with access could inadvertently or maliciously delete critical endpoint specifications.
From the tool's definition Tool name: delete_api_endpoint. Description states: '删除 Apifox 项目中的 HTTP 接口。⚠️ 此操作不可撤销！' which translates to 'Delete HTTP endpoints in Apifox projects.
Documented attack patterns abuse exactly the kind of access delete_api_endpoint 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 delete_api_endpoint:
{
"version": "1",
"default": "deny",
"hide": [
"delete_api_endpoint"
]
}delete_api_endpoint disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
删除 Apifox 项目中的 HTTP 接口。⚠️ 此操作不可撤销！. 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.
Register the Apifox MCP Server MCP server in PolicyLayer and add a rule for delete_api_endpoint: 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.
delete_api_endpoint is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_api_endpoint 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 delete_api_endpoint. 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.
delete_api_endpoint 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.