media.podcast.episodes
List recent episodes for a podcast by feed ID — title, description, publish date, audio URL, duration, season/episode numbers. Use feed ID from search or trending results (PodcastIndex)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/media.podcast.episodes.md
What media.podcast.episodes does on Apibase
AI agents call media.podcast.episodes to retrieve information from Apibase 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 |
|---|---|---|---|
id | integer | Yes | PodcastIndex feed ID (from search or trending results) |
max | integer | — | Number of episodes to return (default 20, max 100) |
since | integer | — | Unix timestamp — only return episodes published after this time |
Parameters from the server's own tool schema.
Why media.podcast.episodes is rated Low
Retrieves podcast episode metadata and audio URLs without modification or side effects.
From the tool's definition List recent episodes for a podcast by feed ID
Attacks that exploit this kind of access
The rule that runs media.podcast.episodes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For media.podcast.episodes, this is the rule to start with:
media.podcast.episodes 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 Apibase, apply this rule, and every media.podcast.episodes call is checked against it from then on.
Questions about media.podcast.episodes
List recent episodes for a podcast by feed ID — title, description, publish date, audio URL, duration, season/episode numbers. Use feed ID from search or trending results (PodcastIndex). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
media.podcast.episodes accepts 3 parameters: id, max, since. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for media.podcast.episodes: 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 Apibase. Nothing to install.
media.podcast.episodes 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 media.podcast.episodes 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 media.podcast.episodes. 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.
media.podcast.episodes is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue