Get current Plex streaming activity — who's watching what, playback state, progress, and quality.
AI agents call tautulli_activity 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 queries and retrieves real-time information about Plex streaming sessions. It has no side effects, does not modify or delete data, and does not execute commands or trigger external operations. It is a pure read operation on existing streaming metrics.
From the tool's definition Tool retrieves current streaming activity data (who's watching what, playback state, progress, and quality) with no indication of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get current Plex streaming activity — who's watching what, playback state, progress, and quality. 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_activity: 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_activity 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_activity 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_activity. 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_activity 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 →