Check the status of an ongoing device authentication flow
AI agents call check_auth_status to retrieve information from Trakt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only checks and returns the status of an existing authentication process. It performs no side effects, creates no data, executes no commands, and cannot delete or move resources. It is a pure read operation that queries the current state of the authentication flow.
From the tool's definition Tool name 'check_auth_status' and description 'Check the status of an ongoing device authentication flow' indicate a query operation that retrieves authentication state without modifying or executing external operations.
Documented attack patterns abuse exactly the kind of access check_auth_status 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 check_auth_status:
{
"version": "1",
"default": "deny",
"tools": {
"check_auth_status": {}
}
}check_auth_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check the status of an ongoing device authentication flow. It is categorised as a Read tool in the Trakt MCP Server, which means it retrieves data without modifying state.
Register the Trakt MCP server in PolicyLayer and add a rule for check_auth_status: 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.
check_auth_status 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 check_auth_status 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 check_auth_status. 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.
check_auth_status 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.