Get user retention metrics for a cohort over time. Returns retention percentages by time period (e.g., day 1, day 7, day 30).
Part of the Amplitude server.
Free to start. No card required.
AI agents call amp_get_retention to retrieve information from Amplitude without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though amp_get_retention only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"amp_get_retention": {}
}
}See the full Amplitude policy for all 25 tools.
These attack patterns abuse exactly the kind of access amp_get_retention gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get user retention metrics for a cohort over time. Returns retention percentages by time period (e.g., day 1, day 7, day 30).. It is categorised as a Read tool in the Amplitude MCP Server, which means it retrieves data without modifying state.
Register the Amplitude MCP server in PolicyLayer and add a rule for amp_get_retention: 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. Nothing to install.
amp_get_retention is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the amp_get_retention 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 amp_get_retention. 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.
amp_get_retention is provided by the Amplitude MCP server (https://gateway.pipeworx.io/amplitude/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 Amplitude tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.