AI agents use tags_create 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.
This tool creates new tags in the analytics system. Creation operations are Write category (reversible modifications). Severity is medium because misconfiguration of tags could affect analytics data collection or tracking behavior, but tags can typically be modified or deleted to correct errors.
From the tool's definition Tool name is 'tags_create' which indicates creation of new tags within Piwik PRO Analytics. The server description explicitly states it 'Supports comprehensive analytics configuration and tag management operations.' Tag creation is a reversible write…
Documented attack patterns abuse exactly the kind of access tags_create 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_create:
{
"version": "1",
"default": "deny",
"tools": {
"tags_create": {
"limits": [
{
"counter": "tags_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}tags_create 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.
tags_create. 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 tags_create: 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_create 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 tags_create 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_create. 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_create 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.