rotten-tomatoes.search
Search Rotten Tomatoes by title or name. Returns matching movies, TV series, and celebrities with slugs, scores, poster URLs, release years, and top-billed cast where available. Cost = 10 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/rotten-tomatoes.search.md
What rotten-tomatoes.search does on Vee3
AI agents call rotten-tomatoes.search 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 |
|---|---|---|---|
limit | object | — | Maximum number of search results to return (1–50, default 20). |
query | string | Yes | Search query for movies, TV series, or celebrities. |
Parameters from the server's own tool schema.
Why rotten-tomatoes.search is rated Low
This tool queries a public entertainment database (Rotten Tomatoes) and retrieves read-only information such as movie metadata, scores, and cast information. There is no ability to create, modify, delete, execute code, or trigger financial transactions. The low token cost (10) and informative description reinforce that this is a simple lookup operation with minimal risk if misused by an AI agent.
From the tool's definition Tool description states 'Search Rotten Tomatoes by title or name' and 'Returns matching movies, TV series, and celebrities with slugs, scores, poster URLs, release years, and top-billed cast where available.' The verb 'Search' and 'Returns' indicate data…
Attacks that exploit this kind of access
The rule that runs rotten-tomatoes.search 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.search, this is the rule to start with:
rotten-tomatoes.search 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.search call is checked against it from then on.
Questions about rotten-tomatoes.search
Search Rotten Tomatoes by title or name. Returns matching movies, TV series, and celebrities with slugs, scores, poster URLs, release years, and top-billed cast where available. Cost = 10 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
rotten-tomatoes.search accepts 2 parameters: limit, query. Required: query. 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.search: 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.search 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.search 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.search. 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.search 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