Run a multi-step churn investigation against your Stripe cancellations. Pre-buckets cancellations into segments (by plan tier, voluntary/involuntary, recency) and lets Claude drill into 1-3 segments before synthesizing a markdown report. More expensive than analyze_stripe_churn (multiple Claude c...
Part of the RetentionCheck server.
Free to start. No card required.
AI agents invoke investigate_churn to trigger processes or run actions in RetentionCheck. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
investigate_churn can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"investigate_churn": {
"limits": [
{
"counter": "investigate_churn_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full RetentionCheck policy for all 5 tools.
These attack patterns abuse exactly the kind of access investigate_churn gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Run a multi-step churn investigation against your Stripe cancellations. Pre-buckets cancellations into segments (by plan tier, voluntary/involuntary, recency) and lets Claude drill into 1-3 segments before synthesizing a markdown report. More expensive than analyze_stripe_churn (multiple Claude calls) but produces deeper analysis. Requires STRIPE_SECRET_KEY and ANTHROPIC_API_KEY.. It is categorised as a Execute tool in the RetentionCheck MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the RetentionCheck MCP server in PolicyLayer and add a rule for investigate_churn: 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 RetentionCheck. Nothing to install.
investigate_churn is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the investigate_churn 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 investigate_churn. 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.
investigate_churn is provided by the RetentionCheck MCP server (@retentioncheck/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 RetentionCheck 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.