批量删除API接口文档，支持单个或多个接口删除。删除前先用apipost_list查看接口列表获取ID
AI agents call apipost_delete to permanently remove resources in ApiPost MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes API documentation records. Deletion is irreversible and cannot be undone. While not financial or directly system-level code execution, the destruction of API documentation represents significant data loss and loss of team knowledge/collaboration artifacts managed by this ApiPost system. The bulk delete capability amplifies the risk of accidental or malicious mass destruction.
From the tool's definition Tool name 'apipost_delete' and description '批量删除API接口文档，支持单个或多个接口删除' (bulk delete API interface documentation, supports deleting single or multiple interfaces) indicates irreversible deletion of API documentation.
Documented attack patterns abuse exactly the kind of access apipost_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ApiPost MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for apipost_delete:
{
"version": "1",
"default": "deny",
"hide": [
"apipost_delete"
]
}apipost_delete 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.
批量删除API接口文档，支持单个或多个接口删除。删除前先用apipost_list查看接口列表获取ID. It is categorised as a Destructive tool in the ApiPost MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ApiPost MCP server in PolicyLayer and add a rule for apipost_delete: 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 ApiPost MCP. Nothing to install.
apipost_delete 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 apipost_delete 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 apipost_delete. 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.
apipost_delete is provided by the ApiPost MCP server (jlcodes99/apipost-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ApiPost MCP, 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.
6 ApiPost MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.