AI agents call delete_schema 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 deletes API schemas with no undo capability, fitting the Destructive category. The high severity reflects that schema deletion could break API documentation and client integrations. While not Financial, it is more severe than Execute or Write due to its irreversible nature and potential to disrupt entire API projects.
From the tool's definition Tool name 'delete_schema' combined with description stating '删除数据模型 (Schema)' (delete data model/schema) and explicit warning '⚠️ 警告: 此操作不可撤销！' (Warning: This operation is irreversible!).
Documented attack patterns abuse exactly the kind of access delete_schema 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_schema:
{
"version": "1",
"default": "deny",
"hide": [
"delete_schema"
]
}delete_schema 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.
删除数据模型 (Schema)。⚠️ 警告: 此操作不可撤销！. 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_schema: 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_schema 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_schema 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_schema. 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_schema 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.