AI agents call tdarr_stats_get_res_hist 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 historical resource statistics from the Tdarr server (CPU, memory, disk usage, etc.). It performs a query operation with no capability to modify, delete, or execute actions. The data retrieved could inform monitoring decisions, but the tool itself has no write, execute, or destructive capabilities. Misuse by an AI agent would be limited to information disclosure about system resources.
From the tool's definition Tool name 'tdarr_stats_get_res_hist' and description 'Get server resource history' indicate a data retrieval operation. The 'get' verb and 'history' object confirm read-only querying of existing metrics with no side effects.
Attacks that exploit this kind of access
Get server resource history. 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_stats_get_res_hist: 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_stats_get_res_hist 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_stats_get_res_hist 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_stats_get_res_hist. 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_stats_get_res_hist 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 →