AI agents use triggers_copy to create or update resources in Piwik PRO MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Piwik PRO MCP Server environment.
Copying a trigger creates new analytics configuration without deleting or overwriting existing data. It is reversible (the copy can be deleted) and does not execute arbitrary code or move financial resources. The operation modifies the analytics setup by adding a new resource, qualifying it as Write.
From the tool's definition Tool name 'triggers_copy' and description 'Copy a trigger, optionally to another app' indicate creation of a new trigger resource by duplicating an existing one. This is a reversible modification operation.
Documented attack patterns abuse exactly the kind of access triggers_copy 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 triggers_copy:
{
"version": "1",
"default": "deny",
"tools": {
"triggers_copy": {
"limits": [
{
"counter": "triggers_copy_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}triggers_copy stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Copy a trigger, optionally to another app. It is categorised as a Write tool in the Piwik PRO MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Piwik PRO MCP Server MCP server in PolicyLayer and add a rule for triggers_copy: 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.
triggers_copy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the triggers_copy 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 triggers_copy. 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.
triggers_copy 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.