rotten-tomatoes.tv_show_episode
Load a single episode by TV series slug (for example breaking-bad), season number, and episode number. Returns episode title, air date, description, and episode Tomatometer score when available. Cost = 5 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/rotten-tomatoes.tv-show-episode.md
What rotten-tomatoes.tv_show_episode does on Vee3
AI agents call rotten-tomatoes.tv_show_episode to retrieve information from Vee3 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tv_show_slug | string | Yes | TV series slug (for example breaking-bad). |
season_number | string | Yes | Season number as one or two digits (for example 1 or 01). |
episode_number | string | Yes | Episode number as one or two digits (for example 1 or 01). |
Parameters from the server's own tool schema.
Why rotten-tomatoes.tv_show_episode is rated Low
The tool queries and retrieves public TV episode metadata from Rotten Tomatoes (title, air date, description, score). No side effects, no data modification, no code execution, no financial transactions. This is a straightforward read operation with minimal blast radius if misused by an agent.
From the tool's definition Tool description states it 'Load[s] a single episode' and 'Returns episode title, air date, description, and episode Tomatometer score' — purely retrieval operations with no modification, deletion, execution, or financial effects.
Attacks that exploit this kind of access
The rule that runs rotten-tomatoes.tv_show_episode safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rotten-tomatoes.tv_show_episode, this is the rule to start with:
rotten-tomatoes.tv_show_episode is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every rotten-tomatoes.tv_show_episode call is checked against it from then on.
Questions about rotten-tomatoes.tv_show_episode
Load a single episode by TV series slug (for example breaking-bad), season number, and episode number. Returns episode title, air date, description, and episode Tomatometer score when available. Cost = 5 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
rotten-tomatoes.tv_show_episode accepts 3 parameters: tv_show_slug, season_number, episode_number. Required: tv_show_slug, season_number, episode_number. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for rotten-tomatoes.tv_show_episode: 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 Vee3. Nothing to install.
rotten-tomatoes.tv_show_episode 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 rotten-tomatoes.tv_show_episode 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 rotten-tomatoes.tv_show_episode. 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.
rotten-tomatoes.tv_show_episode is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue