tautulli_history
AI agents call tautulli_history to retrieve information from Mcp Tautulli without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to be a read-only query into Tautulli (a Plex monitoring application) historical data. All sibling tools are non-destructive information retrieval operations. Without any evidence of write, delete, or execution capabilities, and given the monitoring/tracking nature of the server, this is classified as a Read operation with low severity since it only queries data.
From the tool's definition Tool name is 'tautulli_history' and sibling tools in the server are all read-only query/tracking operations (activity, library_stats, most_watched, platform_stats, plays_by_date, recently_added, search, server_info).
Attacks that exploit this kind of access
tautulli_history. It is categorised as a Read tool in the Mcp Tautulli MCP Server, which means it retrieves data without modifying state.
Register the Mcp Tautulli MCP server in PolicyLayer and add a rule for tautulli_history: 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 Mcp Tautulli. Nothing to install.
tautulli_history 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 tautulli_history 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 tautulli_history. 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.
tautulli_history is provided by the Mcp Tautulli MCP server (lodordev/mcp-tautulli). 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 →