// SCAN REPORT

LinkForty MCP Server

20 tools. 7 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 2 Jul 2026

7 can modify or destroy data

13 read-only

20 tools total

Community server · catalogue entry verified 02/07/2026

How to control LinkForty MCP Server ↓

TOOL MAP

What LinkForty MCP Server exposes to your agents

Read (13) Write / Execute (6) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous LinkForty MCP Server tools

Destructive · High delete_link The delete_link tool irreversibly removes data (the deep link and its associated historical analytics). Write · Medium bulk_create_links This tool creates new deep links in bulk (up to 100 per request), which is a reversible write operation. Write · Medium create_link This tool creates new resources (deep links) with configurable parameters including device-specific URLs, UTM parameters, targeting rules, and attribution windows. Write · Low create_project This tool creates new data (a project) in the LinkForty system, which is a reversible write operation.

7 of LinkForty MCP Server's 20 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control LinkForty MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and LinkForty MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_link": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "bulk_create_links": {
    "limits": [
      {
        "counter": "bulk_create_links_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_app_config": {
    "limits": [
      {
        "counter": "get_app_config_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register LinkForty MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON LINKFORTY →

Instant setup, no code required.

FULL CATALOGUE

All 20 LinkForty MCP Server tools

DESTRUCTIVE 1 tools

Destructive delete_link Permanently delete a deep link by ID. This action cannot be undone — historical click events for the link are

WRITE 6 tools

Write bulk_create_links Create up to 100 deep links in a single request. Each link in the array uses the same shape as create_link. If Write create_link Create a new deep link in LinkForty. Supports device-specific URLs (iOS App Store, Google Play, web fallback), Write create_project Create a new project to group related links. Returns the created project. Use the project ID when creating lin Write create_template Create a new link template. Templates let you define default destinations (iOS/Android/web), UTM parameters, t Write set_default_template Mark a template as the default for the workspace. The default template is used by the SDK when creating links Write update_link Update an existing deep link. All fields are optional — only provided fields are updated. Use this to change d

READ 13 tools

Read get_app_config Get the iOS/Android app configuration for the current workspace, including app scheme, bundle IDs, package nam Read get_current_workspace Get details about the current workspace including subscription tier, member count, link count, project count, Read get_funnel Get the conversion funnel from clicks → installs → events for the workspace. Returns total clicks, unique clic Read get_install_attribution Get install attribution data showing how app installs are linked to clicks via device fingerprinting. Pass a l Read get_link Get a single deep link by ID or short code. Use this to inspect a specific link\ Read get_link_analytics Get detailed analytics for a single deep link. Returns total clicks, unique clicks, time series, and breakdown Read get_overview_analytics Get workspace-wide analytics across all links. Returns total clicks, unique clicks, time series, geo breakdown Read get_sdk_install_snippet Generate a ready-to-paste SDK initialization snippet for a specific mobile platform. The snippet is pre-filled Read get_top_links Get the top performing links in the workspace ranked by total clicks. Returns each link\ Read list_links List deep links in the current workspace. Supports filtering by status (active/inactive), source (dashboard/sd Read list_projects List all projects in the current workspace. Projects are containers for organizing related deep links — for ex Read list_templates List all link templates in the current workspace. Templates define default destinations, UTM parameters, and t Read list_workspaces List all workspaces accessible by the current API key. Note: API keys are scoped to a single workspace, so thi

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about LinkForty MCP Server

Can an AI agent delete data through the LinkForty MCP Server MCP server? +

Yes. The LinkForty MCP Server server exposes 1 destructive tools including delete_link. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through LinkForty MCP Server? +

The LinkForty MCP Server server has 6 write tools including bulk_create_links, create_link, create_project. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach LinkForty MCP Server.

How many tools does the LinkForty MCP Server MCP server expose? +

20 tools across 3 categories: Destructive, Read, Write. 13 are read-only. 7 can modify, create, or delete data.

How do I enforce a policy on LinkForty MCP Server? +

Register the LinkForty MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every LinkForty MCP Server tool call.

Deterministic rules across all 20 LinkForty MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON LINKFORTY →

Instant setup, no code required.

20 LinkForty MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.