AI agents call tdarr_get_subdirectories 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 performs a simple filesystem query to retrieve subdirectory information. It has no side effects, makes no modifications, executes no code, and poses minimal security risk. The only concern is potential information disclosure if an attacker queries sensitive directory structures, but this is inherent to read operations and represents a lower risk compared to write, execute, or destructive operations.
From the tool's definition Tool name 'get_subdirectories' and description 'Get subdirectories of a folder' indicate a read-only query operation that retrieves directory listing information without modifying any data.
Attacks that exploit this kind of access
Get subdirectories of a folder. 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_subdirectories: 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_subdirectories 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_subdirectories 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_subdirectories. 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_subdirectories 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 →