episode_context_bundle

Episode + parent show + neighbouring episodes (prev/next by release date) in one card.

SERVERSpotify SOURCE@novalux12/spotify-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/novalux12-spotify-mcp/episode-context-bundle.md

WHAT IT DOES

What episode_context_bundle does on Spotify

AI agents call episode_context_bundle to retrieve information from Spotify without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why episode_context_bundle is rated Low

Even though episode_context_bundle only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs episode_context_bundle safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Spotify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For episode_context_bundle, this is the rule to start with:

episode_context_bundle Allowed

episode_context_bundle is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "episode_context_bundle": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Spotify, apply this rule, and every episode_context_bundle call is checked against it from then on.

FAQ

Questions about episode_context_bundle

What does the episode_context_bundle tool do? +

Episode + parent show + neighbouring episodes (prev/next by release date) in one card. It is categorised as a Read tool in the Spotify MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on episode_context_bundle? +

Register the Spotify MCP server in PolicyLayer and add a rule for episode_context_bundle: 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 Spotify. Nothing to install.

What risk level is episode_context_bundle? +

episode_context_bundle is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit episode_context_bundle? +

Yes. Add a rate_limit block to the episode_context_bundle 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.

How do I block episode_context_bundle completely? +

Set action: deny in the PolicyLayer policy for episode_context_bundle. 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.

What MCP server provides episode_context_bundle? +

episode_context_bundle is provided by the Spotify MCP server (@novalux12/spotify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Spotify, and thousands of servers like it.

This server

All 544 Spotify tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →