Delete an Intercom Help Center collection. WARNING: This action cannot be undone. The collection and all its contents will be permanently removed.
AI agents call delete_collection to permanently remove resources in Intercom Articles MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently and irreversibly deletes a collection and all nested content without recovery option. This matches the Destructive category definition (irreversibly deletes data, actions that cannot be undone).
From the tool's definition 'Delete an Intercom Help Center collection' and 'This action cannot be undone. The collection and all its contents will be permanently removed.'
Documented attack patterns abuse exactly the kind of access delete_collection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Intercom Articles MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_collection:
{
"version": "1",
"default": "deny",
"hide": [
"delete_collection"
]
}delete_collection 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.
Delete an Intercom Help Center collection. WARNING: This action cannot be undone. The collection and all its contents will be permanently removed. It is categorised as a Destructive tool in the Intercom Articles MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Intercom Articles MCP Server MCP server in PolicyLayer and add a rule for delete_collection: 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 Intercom Articles MCP Server. Nothing to install.
delete_collection 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_collection 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_collection. 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_collection is provided by the Intercom Articles MCP Server MCP server (kaosensei/intercom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Intercom Articles 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.
16 Intercom Articles MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.