podcast_by_feed_url
Get a podcast by feed URL from Podcast Index.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/podcast-by-feed-url.md
What podcast_by_feed_url does on UnClick
AI agents call podcast_by_feed_url to retrieve information from UnClick 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 |
|---|---|---|---|
url | string | Yes | |
api_key | string | — | |
api_secret | string | — |
Parameters from the server's own tool schema.
Why podcast_by_feed_url is rated Low
This tool queries the Podcast Index API to fetch podcast metadata using a feed URL. It performs a read-only lookup operation with no side effects, no data modification, and no code execution. The blast radius of misuse is minimal—an attacker could retrieve podcast information but cannot modify, delete, or trigger external actions. This is a straightforward data retrieval tool.
From the tool's definition Tool description states 'Get a podcast by feed URL' — a retrieval operation with no modification, deletion, or execution of arbitrary code.
Risk signalsAccepts URL/endpoint input (url) · Handles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs podcast_by_feed_url safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For podcast_by_feed_url, this is the rule to start with:
podcast_by_feed_url 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 UnClick, apply this rule, and every podcast_by_feed_url call is checked against it from then on.
Questions about podcast_by_feed_url
Get a podcast by feed URL from Podcast Index. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
podcast_by_feed_url accepts 3 parameters: url, api_key, api_secret. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for podcast_by_feed_url: 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 UnClick. Nothing to install.
podcast_by_feed_url 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 podcast_by_feed_url 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 podcast_by_feed_url. 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.
podcast_by_feed_url is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue