AI agents use checkin_to_show to create or update resources in Trakt — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trakt environment.
This tool records a check-in action (marking a TV show episode as currently being watched) on Trakt.tv. It creates/modifies viewing status data on the platform. While reversible in principle, it writes a new record to the user's activity history. The description is truncated, lowering confidence slightly, but 'Check in' clearly indicates a write operation.
From the tool's definition Check in to a TV show episode you
Documented attack patterns abuse exactly the kind of access checkin_to_show 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 checkin_to_show:
{
"version": "1",
"default": "deny",
"tools": {
"checkin_to_show": {
"limits": [
{
"counter": "checkin_to_show_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}checkin_to_show stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check in to a TV show episode you. It is categorised as a Write tool in the Trakt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Trakt MCP server in PolicyLayer and add a rule for checkin_to_show: 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.
checkin_to_show 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 checkin_to_show 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 checkin_to_show. 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.
checkin_to_show 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.