Get what a user is currently watching
AI agents call get_user_watching 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 information about a user's current viewing activity. It performs a query operation with no capability to modify, delete, or execute actions. The data returned is informational only, making it a Read operation. Severity is low because exposure of viewing history has minimal impact compared to other risk categories, though minor privacy concerns exist if accessed without authorization.
From the tool's definition Tool name 'get_user_watching' and description 'Get what a user is currently watching' indicate retrieval of user viewing data with no modification or side effects.
Attacks that exploit this kind of access
Get what a user is currently watching. 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_user_watching: 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_user_watching 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_user_watching 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_user_watching. 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_user_watching 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 →