// SCAN REPORT

Trackings MCP Server

8 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

2 can modify or destroy data

6 read-only

8 tools total

Community server · catalogue entry verified 03/07/2026

How to control Trackings MCP Server ↓

TOOL MAP

What Trackings MCP Server exposes to your agents

Read (6) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Trackings MCP Server tools

Execute · Medium trigger_scan_run This tool triggers execution of a scan operation on an external service (trackings.ai). Write · Medium create_scan This tool creates scan configurations, which is a write operation that modifies state by adding new records.

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

POLICY

How to control Trackings MCP Server

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

Rate limit write operations

{
  "create_scan": {
    "limits": [
      {
        "counter": "create_scan_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_credits": {
    "limits": [
      {
        "counter": "get_credits_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 Trackings 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 TRACKINGS →

Instant setup, no code required.

FULL CATALOGUE

All 8 Trackings MCP Server tools

EXECUTE 1 tools

Execute trigger_scan_run Trigger a scan run for an existing scan configuration

WRITE 1 tools

Write create_scan Create a scan configuration

READ 6 tools

Read get_credits Get current credit balance and subscription info Read get_scan_results Get consolidated keyword results for a scan run Read get_scan_run Get details for a scan run Read list_projects List all projects in Trackings Read list_scan_runs List scan runs by project or scan Read list_scans List scans for a project

EXPLORE

Related servers

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

FAQ

Questions about Trackings MCP Server

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

The Trackings MCP Server server has 1 write tools including create_scan. 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 Trackings MCP Server.

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

8 tools across 3 categories: Execute, Read, Write. 6 are read-only. 2 can modify, create, or delete data.

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

Register the Trackings 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 Trackings MCP Server tool call.

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

ENFORCE POLICY ON TRACKINGS →

Instant setup, no code required.

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