AI agents call tdarr_debug_vars to retrieve information from Tdarr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves debug information from the Tdarr transcoding system. It has no side effects, does not modify state, and does not trigger external operations. It is purely diagnostic/observational in nature, fitting the 'Read' category. Severity is low because debug information exposure is typically low-risk unless it contains sensitive credentials, but debug data itself is non-destructive and read-only.
From the tool's definition Tool name 'tdarr_debug_vars' and description 'Get various debug info by type' indicate a retrieval operation. The verb 'Get' and context of 'debug info' shows this is a read-only operation that queries and returns debugging information without modification.
Attacks that exploit this kind of access
Get various debug info by type. It is categorised as a Read tool in the Tdarr MCP Server, which means it retrieves data without modifying state.
Register the Tdarr MCP server in PolicyLayer and add a rule for tdarr_debug_vars: 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 Tdarr. Nothing to install.
tdarr_debug_vars 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 tdarr_debug_vars 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 tdarr_debug_vars. 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.
tdarr_debug_vars is provided by the Tdarr MCP server (maximeallanic/tdarr-mcp). 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 →