add_to_history · Trakt MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_to_history does on Trakt MCP Server

AI agents use add_to_history to create or update resources in Trakt MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trakt MCP Server environment.

WHY IT NEEDS A POLICY

Why add_to_history needs a policy

This tool creates or updates a user's viewing history, which is reversible data modification. It does not execute arbitrary code, delete data irreversibly, involve financial transactions, or perform system-level operations. The impact is limited to personal entertainment tracking metadata.

From the tool's definition Tool name 'add_to_history' with description 'Mark movies or episodes as watched' indicates creating/modifying a watch history record.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_to_history Rate-limited

add_to_history stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_to_history": {
      "limits": [
        {
          "counter": "add_to_history_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Trakt MCP Server, so you can run agents against it safely.

FAQ

Questions about add_to_history

What does the add_to_history tool do? +

Mark movies or episodes as watched. It is categorised as a Write tool in the Trakt MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_to_history? +

Register the Trakt MCP Server MCP server in PolicyLayer and add a rule for add_to_history: 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 Trakt MCP Server. Nothing to install.

What risk level is add_to_history? +

add_to_history is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_to_history? +

Yes. Add a rate_limit block to the add_to_history 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.

How do I block add_to_history completely? +

Set action: deny in the PolicyLayer policy for add_to_history. 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.

What MCP server provides add_to_history? +

add_to_history is provided by the Trakt MCP Server MCP server (kud/mcp-trakt). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.