// SCAN REPORT

Trakt MCP Server

53 tools. 14 can modify or destroy data without limits.

6 destructive tools with no built-in limits. Policy required.

Last updated: 29 Jun 2026

14 can modify or destroy data

39 read-only

53 tools total

Community server · catalogue entry verified 29/06/2026

How to control Trakt MCP Server ↓

TOOL MAP

What Trakt MCP Server exposes to your agents

Read (39) Write / Execute (8) Destructive / Financial (6)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Trakt MCP Server tools

Destructive · Medium delete_checkin Canceling/deleting a checkin is an irreversible removal of an active check-in state. Destructive · High delete_playback The tool performs an irreversible deletion operation on a user's playback data (removing a paused playback record). Destructive · High remove_from_collection Removing items from a collection is an irreversible deletion of user data. Destructive · High remove_from_history This tool permanently deletes user data (watch history entries) that cannot be recovered or undone.

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

POLICY

How to control Trakt MCP Server

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

Deny destructive operations

{
  "delete_checkin": {
    "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

{
  "add_rating": {
    "limits": [
      {
        "counter": "add_rating_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_all_movie_calendar": {
    "limits": [
      {
        "counter": "get_all_movie_calendar_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 Trakt 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 TRAKT →

Instant setup, no code required.

FULL CATALOGUE

All 53 Trakt MCP Server tools

DESTRUCTIVE 6 tools

Destructive delete_checkin Cancel the current active checkin Destructive delete_playback Delete a paused playback entry Destructive remove_from_collection Remove movies, shows, or episodes from the user Destructive remove_from_history Remove items from watch history Destructive remove_from_watchlist Remove movies, shows, or episodes from the watchlist Destructive remove_rating Remove ratings from movies, shows, or episodes

WRITE 8 tools

Write add_rating Rate movies, shows, seasons, or episodes (1–10) Write add_to_collection Add movies, shows, or episodes to the user Write add_to_history Mark movies or episodes as watched Write add_to_watchlist Add movies, shows, or episodes to the watchlist Write checkin Check in to a movie or episode you are watching right now Write scrobble_pause Pause scrobbling — call when playback is paused to save progress Write scrobble_start Start scrobbling — call when playback begins to track what you are watching Write scrobble_stop Stop scrobbling — call when playback ends to record the watch

READ 39 tools

EXPLORE

Related servers

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

FAQ

Questions about Trakt MCP Server

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

Yes. The Trakt MCP Server server exposes 6 destructive tools including delete_checkin, delete_playback, remove_from_collection. 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 Trakt MCP Server? +

The Trakt MCP Server server has 8 write tools including add_rating, add_to_collection, add_to_history. 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 Trakt MCP Server.

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

53 tools across 4 categories: Destructive, Execute, Read, Write. 39 are read-only. 14 can modify, create, or delete data.

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

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

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

ENFORCE POLICY ON TRAKT →

Instant setup, no code required.

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