AI agents call remove_from_history to permanently remove resources in Trakt — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool deletes user data (viewing history entries) irreversibly. While the description is empty, the function name combined with the server's purpose (managing Trakt viewing history) makes the destructive nature clear. This is more severe than Write (which is reversible) because deletions cannot be easily recovered. High severity due to potential loss of user's entertainment activity records.
From the tool's definition Tool name 'remove_from_history' indicates irreversible deletion of viewing history records. The verb 'remove' combined with 'history' context signifies permanent data removal that cannot be undone.
Documented attack patterns abuse exactly the kind of access remove_from_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trakt, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_from_history:
{
"version": "1",
"default": "deny",
"hide": [
"remove_from_history"
]
}remove_from_history disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
remove_from_history. It is categorised as a Destructive tool in the Trakt MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Trakt 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. 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 (wwiens/trakt_mcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 77 Trakt tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
77 Trakt tools catalogued and risk-classified — across an index of 42,500+ MCP servers.