AI agents call tdarr_list_footprint_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 retrieves and queries job report data for a given footprintId without modifying, deleting, or executing any operations. It fits the Read category definition: 'retrieves or queries data; no side effects'. The blast radius of misuse is minimal—an attacker could only view existing transcoding reports, not affect system state or resources.
From the tool's definition Tool name contains 'list' and description states 'List all job reports', indicating a retrieval operation with no side effects. The footprintId parameter is a query filter, not a command that modifies or executes operations.
Attacks that exploit this kind of access
List all job reports for a specific footprintId. 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_list_footprint_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_list_footprint_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_list_footprint_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_list_footprint_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_list_footprint_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 →