analytics_annotations_delete

THE RISK

Critical Risk

Why analytics_annotations_delete needs a policy

This tool permanently removes data (user annotations) from the Piwik PRO Analytics system. Deletion operations are irreversible and cannot be undone, which places this in the Destructive category. The severity is high because an AI agent could maliciously or accidentally delete important analytics annotations that provide context or documentation for the analytics configuration.

From the tool's definition The tool name is 'analytics_annotations_delete' and the description states 'Delete a user annotation by ID.' The verb 'delete' combined with the irreversible nature of removing an annotation makes this a destructive operation.

Documented attack patterns abuse exactly the kind of access analytics_annotations_delete gives an agent:

POLICY

How to control analytics_annotations_delete

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 analytics_annotations_delete:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "analytics_annotations_delete"
  ]
}

analytics_annotations_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Piwik PRO MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Piwik PRO MCP Server tools

Destructive tags_delete Delete a tag from Piwik PRO Tag Manager. Destructive tracker_settings_app_delete tracker_settings_app_delete Destructive triggers_delete Delete a trigger from Piwik PRO Tag Manager. Destructive variables_delete variables_delete Execute analytics_query_execute analytics_query_execute Execute versions_publish_draft versions_publish_draft Write analytics_annotations_create analytics_annotations_create Write analytics_annotations_update analytics_annotations_update

All 66 Piwik PRO MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Piwik PRO MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about analytics_annotations_delete

What does the analytics_annotations_delete tool do? +

Delete a user annotation by ID. 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.

How do I enforce a policy on analytics_annotations_delete? +

Register the Piwik PRO MCP Server MCP server in PolicyLayer and add a rule for analytics_annotations_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.

What risk level is analytics_annotations_delete? +

analytics_annotations_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit analytics_annotations_delete? +

Yes. Add a rate_limit block to the analytics_annotations_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.

How do I block analytics_annotations_delete completely? +

Set action: deny in the PolicyLayer policy for analytics_annotations_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.

What MCP server provides analytics_annotations_delete? +

analytics_annotations_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.

Enforce policy on every Piwik PRO MCP Server tool call.

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.

CHECK YOUR STACK →