srgssr_video_get_episodes
AI agents call srgssr_video_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.
This tool retrieves video episode information from a public API. It follows the query/retrieval pattern of sibling 'get_' tools and the server's stated purpose of providing metadata access. No side effects, modifications, or destructive operations are indicated. Classification as Read is appropriate for metadata retrieval from public APIs.
From the tool's definition Tool name 'srgssr_video_get_episodes' indicates retrieval of episode metadata. Sibling tools like 'srgssr_audio_get_episodes', 'srgssr_video_get_shows', and 'srgssr_audio_get_livestreams' are all data retrieval operations from public SRG SSR APIs.
Attacks that exploit this kind of access
srgssr_video_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_video_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_video_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_video_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_video_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_video_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 →