srgssr_audio_get_episodes
AI agents call srgssr_audio_get_episodes to retrieve information from Pypi:srgssr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' prefix and the context of a public SRG SSR media metadata API strongly indicate this tool retrieves audio episode information without side effects. No modification, deletion, execution, or financial transaction is implied. Confidence is slightly reduced due to the empty description, but the naming convention and sibling tool patterns provide strong contextual evidence.
From the tool's definition Tool name 'srgssr_audio_get_episodes' indicates a retrieval/query operation ('get') for audio episode data from a public API server.
Attacks that exploit this kind of access
srgssr_audio_get_episodes. It is categorised as a Read tool in the Pypi:srgssr MCP Server, which means it retrieves data without modifying state.
Register the Pypi:srgssr MCP server in PolicyLayer and add a rule for srgssr_audio_get_episodes: 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 Pypi:srgssr. Nothing to install.
srgssr_audio_get_episodes 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 srgssr_audio_get_episodes 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 srgssr_audio_get_episodes. 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.
srgssr_audio_get_episodes is provided by the Pypi:srgssr MCP server (malkreide/srgssr-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 →