Get the conversion funnel from clicks → installs → events for the workspace. Returns total clicks, unique clicks, total/attributed installs, click-to-install conversion rate, average/median/p75/p95 time to install, and the top converting links. Useful for understanding overall campaign efficiency...
AI agents call get_funnel to retrieve information from LinkForty MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries analytics data from the workspace conversion funnel. It has no side effects, creates no data modifications, and performs no destructive or financial operations. The 'analytics:installs' permission requirement confirms it is read-only access to existing analytics data.
From the tool's definition Tool description uses 'Get' and 'Returns' language indicating data retrieval only. Provides funnel analytics metrics (clicks, installs, conversion rates, timing statistics) without modifying, creating, or deleting any data.
Attacks that exploit this kind of access
Get the conversion funnel from clicks → installs → events for the workspace. Returns total clicks, unique clicks, total/attributed installs, click-to-install conversion rate, average/median/p75/p95 time to install, and the top converting links. Useful for understanding overall campaign efficiency. Note: requires the analytics:installs permission. It is categorised as a Read tool in the LinkForty MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LinkForty MCP Server MCP server in PolicyLayer and add a rule for 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 LinkForty MCP Server. Nothing to install.
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 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 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.
get_funnel is provided by the LinkForty MCP Server MCP server (linkforty/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_funnel is one line of LinkForty MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →