AI agents call tags_delete to permanently remove resources in Piwik PRO 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 tags from the tag management system. Tags in analytics platforms typically control tracking, pixel firing, and data collection behavior. Deleting a tag cannot be undone and could disrupt analytics data collection pipelines. An AI agent with unconstrained access could inadvertently or maliciously delete critical tags, breaking monitoring and measurement infrastructure.
From the tool's definition Tool name explicitly includes 'delete' and description states 'Delete a tag from Piwik PRO Tag Manager.' Deletion operations are irreversible.
Documented attack patterns abuse exactly the kind of access tags_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Piwik PRO MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for tags_delete:
{
"version": "1",
"default": "deny",
"hide": [
"tags_delete"
]
}tags_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.
Delete a tag from Piwik PRO Tag Manager. It is categorised as a Destructive tool in the Piwik PRO MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Piwik PRO MCP Server MCP server in PolicyLayer and add a rule for tags_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 Piwik PRO MCP Server. Nothing to install.
tags_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 tags_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 tags_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.
tags_delete is provided by the Piwik PRO MCP Server MCP server (piwikpro/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Piwik PRO 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.
66 Piwik PRO MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.