Generate audio for a podcast episode that already has text content. This is the second stage of two-stage generation. The episode must have contentStatus=text-success. You can optionally provide customScripts parameter to override the generated scripts when generating audio. NOTE: This is the ONL...
AI agents invoke generate_podcast_audio to trigger actions in ListenHub MCP Server. 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.
This tool triggers an external audio generation process, making it an Execute category. It runs an operation whose effects depend on arguments (the podcast episode ID and optional custom scripts). It is not purely destructive or financial, but it does execute an external pipeline that produces audio artifacts.
From the tool's definition 'Generate audio for a podcast episode' and 'second stage of two-stage generation' — triggers external audio generation operation; also 'optionally provide customScripts parameter to override the generated scripts when generating audio'
Documented attack patterns abuse exactly the kind of access generate_podcast_audio gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ListenHub MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_podcast_audio:
{
"version": "1",
"default": "deny",
"tools": {
"generate_podcast_audio": {
"limits": [
{
"counter": "generate_podcast_audio_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}generate_podcast_audio 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.
Free to start. No card required.
Generate audio for a podcast episode that already has text content. This is the second stage of two-stage generation. The episode must have contentStatus=text-success. You can optionally provide customScripts parameter to override the generated scripts when generating audio. NOTE: This is the ONLY way to use modified scripts - there is no separate tool to edit scripts after generation. It is categorised as a Execute tool in the ListenHub MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ListenHub MCP Server MCP server in PolicyLayer and add a rule for generate_podcast_audio: 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 ListenHub MCP Server. Nothing to install.
generate_podcast_audio 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 generate_podcast_audio 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 generate_podcast_audio. 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.
generate_podcast_audio is provided by the ListenHub MCP Server MCP server (marswaveai/listenhub-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ListenHub MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 ListenHub MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.