Lists all unique seasons in the video library (e.g.
AI agents call list_unique_seasons to retrieve information from Video Metadata MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from the video metadata database to enumerate unique season values. It performs no side effects, creates no resources, modifies no data, and executes no external operations. It is a straightforward Read operation with minimal security risk.
From the tool's definition Tool name 'list_unique_seasons' and description indicate it 'Lists all unique seasons in the video library' — a retrieval operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Lists all unique seasons in the video library (e.g. It is categorised as a Read tool in the Video Metadata MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Video Metadata MCP Server MCP server in PolicyLayer and add a rule for list_unique_seasons: 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 Video Metadata MCP Server. Nothing to install.
list_unique_seasons 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 list_unique_seasons 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 list_unique_seasons. 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.
list_unique_seasons is provided by the Video Metadata MCP Server MCP server (stich-studios/metadata-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 →