This record as markdown: /tools/kh0pper-crow/crow-iptv-favorite.md
What crow_iptv_favorite does on Crow
AI agents use crow_iptv_favorite to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
Why crow_iptv_favorite is rated Medium
This tool modifies user preference data (favorites list) by adding or removing channels. It creates or updates a reversible record in a favorites list. Removal from favorites is not truly destructive (it's a preference toggle, not data deletion), so Write is the most appropriate category. Blast radius is low as it only affects personal/user-level preference data.
From the tool's definition Add or remove a channel from favorites
Attacks that exploit this kind of access
The rule that runs crow_iptv_favorite safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_iptv_favorite, this is the rule to start with:
crow_iptv_favorite stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_iptv_favorite call is checked against it from then on.
Questions about crow_iptv_favorite
Add or remove a channel from favorites. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for crow_iptv_favorite: 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 Crow. Nothing to install.
crow_iptv_favorite is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the crow_iptv_favorite 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 crow_iptv_favorite. 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.
crow_iptv_favorite is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue