Rate movies, shows, seasons, or episodes (1–10)
AI agents use add_rating 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 rating data in Trakt's database, which is reversible—ratings can be updated or deleted. It does not execute code, delete data irreversibly, or involve financial transactions. It is a Write operation with low severity because misuse only affects the user's own rating records without broad destructive impact or external side effects.
From the tool's definition add_rating creates or modifies user rating data (1–10 scale) for movies, shows, seasons, or episodes. The verb 'add' and the action of recording ratings indicates creation/modification of user preferences.
Attacks that exploit this kind of access
Rate movies, shows, seasons, or episodes (1–10). 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_rating: 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_rating 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_rating 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_rating. 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_rating 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 →