Remove items from watch history
AI agents call remove_from_history to permanently remove resources in Trakt MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes user data (watch history entries) that cannot be recovered or undone. While not as critical as financial operations, destruction of user data records represents a high-severity risk. An AI agent with unchecked access could erase a user's entire viewing history without authorization.
From the tool's definition Tool name is 'remove_from_history' with description 'Remove items from watch history'. The verb 'remove' combined with 'from history' indicates irreversible deletion of historical viewing records.
Attacks that exploit this kind of access
Remove items from watch history. It is categorised as a Destructive tool in the Trakt MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Trakt MCP Server MCP server in PolicyLayer and add a rule for remove_from_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.
remove_from_history is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_from_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.
Set action: deny in the PolicyLayer policy for remove_from_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.
remove_from_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.
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 →