amplitude_run_segmentation · Integrations MCP: Risk & Policy

WHAT IT DOES

What amplitude_run_segmentation does on Integrations MCP

AI agents invoke amplitude_run_segmentation to trigger actions in Integrations MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why amplitude_run_segmentation needs a policy

The verb 'run' indicates execution rather than simple retrieval. Segmentation operations in analytics platforms typically execute complex queries or data operations whose effects depend on parameters. While not destructive (data is not deleted) or financial, this is an Execute-category tool because it actively processes/transforms analytics data rather than passively reading it.

From the tool's definition Tool name 'amplitude_run_segmentation' indicates execution of a segmentation operation; description is empty, limiting evidence. Amplitude segmentation involves running queries/operations that may affect data processing or analytics workflows.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

amplitude_run_segmentation Rate-limited

amplitude_run_segmentation stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "amplitude_run_segmentation": {
      "limits": [
        {
          "counter": "amplitude_run_segmentation_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Integrations MCP, so you can run agents against it safely.

FAQ

Questions about amplitude_run_segmentation

What does the amplitude_run_segmentation tool do? +

amplitude_run_segmentation. It is categorised as a Execute tool in the Integrations MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on amplitude_run_segmentation? +

Register the Integrations MCP server in PolicyLayer and add a rule for amplitude_run_segmentation: 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 Integrations MCP. Nothing to install.

What risk level is amplitude_run_segmentation? +

amplitude_run_segmentation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit amplitude_run_segmentation? +

Yes. Add a rate_limit block to the amplitude_run_segmentation 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.

How do I block amplitude_run_segmentation completely? +

Set action: deny in the PolicyLayer policy for amplitude_run_segmentation. 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.

What MCP server provides amplitude_run_segmentation? +

amplitude_run_segmentation is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.