Get install attribution data showing how app installs are linked to clicks via device fingerprinting. Pass a linkId to get installs for a specific link, or omit it for workspace-wide stats. Returns total installs, attributed vs organic split, attribution rate, time series, platform breakdown, and...
AI agents call get_install_attribution 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 is a pure read operation that retrieves historical analytics and attribution data. It has no side effects, cannot modify data, and does not execute external operations. The permission requirement (analytics:installs) is a read-level access control, not an indicator of destructive capability. Low severity because misuse would only expose analytics visibility, not enable data manipulation or code execution.
From the tool's definition Tool retrieves and queries install attribution data with no modification capabilities. Verbs used: 'Get', 'Returns'.
Attacks that exploit this kind of access
Get install attribution data showing how app installs are linked to clicks via device fingerprinting. Pass a linkId to get installs for a specific link, or omit it for workspace-wide stats. Returns total installs, attributed vs organic split, attribution rate, time series, platform breakdown, and recent installs. 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_install_attribution: 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_install_attribution 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_install_attribution 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_install_attribution. 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_install_attribution 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →