Track a page view event in Amplitude
AI agents use amplitude_track_pageview to create or update resources in Amplitude MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amplitude MCP Server environment.
This tool writes analytics data (page view events) to Amplitude. It creates new event records but does not delete or overwrite existing data, making it a Write operation. The blast radius is low since misuse would only result in inaccurate/polluted analytics data.
From the tool's definition Track a page view event in Amplitude
Documented attack patterns abuse exactly the kind of access amplitude_track_pageview gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amplitude MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for amplitude_track_pageview:
{
"version": "1",
"default": "deny",
"tools": {
"amplitude_track_pageview": {
"limits": [
{
"counter": "amplitude_track_pageview_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}amplitude_track_pageview 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.
Track a page view event in Amplitude. It is categorised as a Write tool in the Amplitude MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amplitude MCP Server MCP server in PolicyLayer and add a rule for amplitude_track_pageview: 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 Amplitude MCP Server. Nothing to install.
amplitude_track_pageview 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 amplitude_track_pageview 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 amplitude_track_pageview. 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.
amplitude_track_pageview is provided by the Amplitude MCP Server MCP server (moonbirdai/amplitude-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amplitude 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.
5 Amplitude MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.