tracker_settings_app_delete
AI agents call tracker_settings_app_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.
The 'delete' operation in the name indicates this tool removes data irreversibly. In an analytics platform, deleting tracker settings or app configurations cannot be easily undone and would impact data collection or system functionality. This is more severe than Write (reversible modification) and qualifies as Destructive.
From the tool's definition Tool name 'tracker_settings_app_delete' explicitly contains 'delete'. No description provided, but the name and server context (Piwik PRO Analytics management) indicate irreversible deletion of tracker settings or app configuration.
Documented attack patterns abuse exactly the kind of access tracker_settings_app_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 tracker_settings_app_delete:
{
"version": "1",
"default": "deny",
"hide": [
"tracker_settings_app_delete"
]
} tracker_settings_app_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.
tracker_settings_app_delete. 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 tracker_settings_app_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.
tracker_settings_app_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 tracker_settings_app_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 tracker_settings_app_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.
tracker_settings_app_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.