Remove a podcast from the tracking list
AI agents call remove_tracking to permanently remove resources in MCP Podcast Scraper — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a podcast from the tracking list is an irreversible deletion of the tracking record. Once removed, any tracking state (e.g., which episodes have been seen) is lost. This qualifies as Destructive. Severity is medium since it affects tracking metadata rather than core content like transcripts, but the action cannot be undone.
From the tool's definition 'Remove a podcast from the tracking list' — permanently removes tracking entry for a podcast
Attacks that exploit this kind of access
Remove a podcast from the tracking list. It is categorised as a Destructive tool in the MCP Podcast Scraper MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Podcast Scraper MCP server in PolicyLayer and add a rule for remove_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.
remove_tracking is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_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 →