This record as markdown: /tools/io-github-heznpc-iconnect/tv-search.md
What tv_search does on Iconnect
AI agents call tv_search to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why tv_search is rated Low
This tool queries a database or search index for movies and TV shows matching user input. It returns results without side effects, making it a Read operation. The blast radius is minimal: worst case, the user receives irrelevant search results. No data is created, modified, deleted, or financial transactions occur.
From the tool's definition Tool name is 'tv_search' and description states it 'Search movies and TV shows by name or show title' — a pure retrieval operation with no modification, deletion, or execution of arbitrary code.
Attacks that exploit this kind of access
The rule that runs tv_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tv_search, this is the rule to start with:
tv_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 Iconnect, apply this rule, and every tv_search call is checked against it from then on.
Questions about tv_search
Search movies and TV shows by name or show title. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for tv_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 Iconnect. Nothing to install.
tv_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 tv_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 tv_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.
tv_search is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue