Delete a page template.
AI agents call delete_template to permanently remove resources in Collectives — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion operations are categorized as Destructive because they irreversibly remove data that cannot be recovered through normal application means. While the blast radius is limited to a single template rather than bulk data, the irreversible nature of deletion and the potential impact on workflows that depend on the template (if it is in use or referenced) warrants a 'high' severity classification.
From the tool's definition Tool name is 'delete_template' which explicitly performs a deletion action. The description states 'Delete a page template.' indicating irreversible removal of a template resource.
Attacks that exploit this kind of access
Delete a page template. It is categorised as a Destructive tool in the Collectives MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Collectives MCP server in PolicyLayer and add a rule for delete_template: 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 Collectives. Nothing to install.
delete_template 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_template 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_template. 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_template is provided by the Collectives MCP server (megamaced/nc_collectives-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →