Add movies, shows, or episodes to the user
AI agents use add_to_collection 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.
This tool creates or modifies user data (a collection) reversibly. It does not delete, execute arbitrary code, move money, or have irreversible side effects. The operation can be undone by removing items from the collection. Therefore, it is classified as Write with low severity due to its limited blast radius — misuse would only affect the user's own collection metadata on Trakt.tv.
From the tool's definition Tool name contains 'add_to' and description states 'Add movies, shows, or episodes to the user' — this is a create/modify operation that adds items to a user collection.
Attacks that exploit this kind of access
Add movies, shows, or episodes to the user. 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.
Register the Trakt MCP Server MCP server in PolicyLayer and add a rule for add_to_collection: 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.
add_to_collection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_to_collection 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 add_to_collection. 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.
add_to_collection 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.
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 →