AI agents call tdarr_search_job_reports 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 queries job report data from the Tdarr system. Searching is inherently a read operation—it retrieves information without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal: an attacker could gain visibility into transcoding job history but cannot alter system state, execute code, or cause irreversible changes.
From the tool's definition Tool name 'tdarr_search_job_reports' and description 'Search job reports' indicate a query/retrieval operation with no side effects. Searching is a read-only operation that retrieves data without modification or execution.
Attacks that exploit this kind of access
Search job reports. 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_search_job_reports: 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_search_job_reports 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_search_job_reports 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_search_job_reports. 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_search_job_reports 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 →