AI agents call get_transcode_settings to retrieve information from PlexMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing configuration data (transcode settings for a quality profile) without creating, modifying, deleting, or executing any operations. It is a straightforward read operation on media server settings, posing minimal security risk if misused by an agent.
From the tool's definition Tool name is 'get_transcode_settings' and description states 'Get current transcode settings' — the verb 'Get' and use of 'current' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get current transcode settings for a quality profile. It is categorised as a Read tool in the PlexMCP MCP Server, which means it retrieves data without modifying state.
Register the Plex MCP server in PolicyLayer and add a rule for get_transcode_settings: 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 PlexMCP. Nothing to install.
get_transcode_settings 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 get_transcode_settings 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 get_transcode_settings. 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.
get_transcode_settings is provided by the Plex MCP server (sandraschi/plexmcp). 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 →