Get all movies the authenticated user has watched with play counts
AI agents call get_watched_movies to retrieve information from Trakt MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical viewing data for the authenticated user. It queries existing information about watched movies and their play counts without creating, modifying, deleting, or executing any operations. This is a straightforward read operation with minimal security risk—it only exposes user's own viewing history that they've already tracked on Trakt.tv.
From the tool's definition Tool name 'get_watched_movies' and description 'Get all movies the authenticated user has watched with play counts' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get all movies the authenticated user has watched with play counts. It is categorised as a Read tool in the Trakt MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Trakt MCP Server MCP server in PolicyLayer and add a rule for get_watched_movies: 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.
get_watched_movies is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_watched_movies 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 get_watched_movies. 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.
get_watched_movies 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 →