List all podcasts currently being tracked
AI agents call list_tracking to retrieve information from MCP Podcast Scraper without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about tracked podcasts without modifying, deleting, or executing any operations. It is a pure read operation with minimal risk—the worst outcome of misuse would be exposure of the list of tracked podcasts, which is low-severity information disclosure.
From the tool's definition Tool name 'list_tracking' and description 'List all podcasts currently being tracked' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all podcasts currently being tracked. It is categorised as a Read tool in the MCP Podcast Scraper MCP Server, which means it retrieves data without modifying state.
Register the MCP Podcast Scraper MCP server in PolicyLayer and add a rule for list_tracking: 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 MCP Podcast Scraper. Nothing to install.
list_tracking 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 list_tracking 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 list_tracking. 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.
list_tracking is provided by the MCP Podcast Scraper MCP server (walid-koleilat/mcp-podcast-scraper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →