crow_media_listen
Generate or retrieve TTS audio for an article. Requires node-edge-tts package (npm install node-edge-tts).
This record as markdown: /tools/kh0pper-crow/crow-media-listen.md
What crow_media_listen does on Crow
AI agents invoke crow_media_listen to trigger actions in Crow. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why crow_media_listen is rated High
This tool generates TTS audio, which involves executing an external process (node-edge-tts) to synthesize speech. It triggers an external operation whose effects depend on arguments (the article content). It goes beyond a simple read/write as it runs an external package to produce audio output, placing it in the Execute category.
From the tool's definition 'Generate or retrieve TTS audio for an article. Requires node-edge-tts package (npm install node-edge-tts)'
Attacks that exploit this kind of access
The rule that runs crow_media_listen 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_media_listen, this is the rule to start with:
crow_media_listen stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_media_listen call is checked against it from then on.
Questions about crow_media_listen
Generate or retrieve TTS audio for an article. Requires node-edge-tts package (npm install node-edge-tts). It is categorised as a Execute tool in the Crow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Crow MCP server in PolicyLayer and add a rule for crow_media_listen: 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_media_listen is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the crow_media_listen 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_media_listen. 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_media_listen 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