amplitude_get_funnel
A read tool on the Integrations MCP server.
This record as markdown: /tools/shriram-vasudevan-integrations-mcp/amplitude-get-funnel.md
What amplitude_get_funnel does on Integrations MCP
AI agents call amplitude_get_funnel to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why amplitude_get_funnel is rated Low
The 'get' verb combined with Amplitude's analytics context strongly indicates this retrieves funnel metrics without modifying data. Funnel analysis is a read-only analytics operation that queries aggregated user journey data. While the description is empty, the naming pattern and sibling tools provide sufficient context to classify with high confidence as a Read operation.
From the tool's definition Tool name 'amplitude_get_funnel' contains the verb 'get', which indicates data retrieval. The Amplitude context confirms this is an analytics platform where funnel analysis retrieves aggregated user behavior data.
Attacks that exploit this kind of access
The rule that runs amplitude_get_funnel safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For amplitude_get_funnel, this is the rule to start with:
amplitude_get_funnel is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every amplitude_get_funnel call is checked against it from then on.
Questions about amplitude_get_funnel
amplitude_get_funnel is a read tool on the Integrations MCP server. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for amplitude_get_funnel: 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.
amplitude_get_funnel 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 amplitude_get_funnel 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_get_funnel. 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_get_funnel 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.
More on Integrations, and thousands of servers like it.
This server
Across the catalogue