AI agents call tdarr_get_process_info 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 process metadata from the Tdarr transcoding system. It displays information about running processes and their hierarchical relationships but does not create, modify, delete, or execute any operations. It is a passive monitoring/diagnostic function with no blast radius if misused by an AI agent, as it cannot affect system state or trigger actions.
From the tool's definition Tool name 'tdarr_get_process_info' and description 'Get process information from server and nodes with child process relationships' indicate data retrieval with no modification or execution.
Attacks that exploit this kind of access
Get process information from server and nodes with child process relationships. 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_get_process_info: 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_get_process_info 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_get_process_info 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_get_process_info. 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_get_process_info 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 →