spotify_home
Retrieve Spotify home sections. Returns normalized shelves and items from Spotify's Web Player home Pathfinder response. The endpoint fetches anonymous Spotify credentials at request time; caller-supplied Spotify bearer or client tokens are not required.
This record as markdown: /tools/crawlora-mcp/spotify-home.md
What spotify_home does on Crawlora
AI agents call spotify_home to retrieve information from Crawlora 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 |
|---|---|---|---|
sp_t | string | — | Optional Spotify session token. A random UUID is generated when omitted |
facet | string | — | Optional Spotify home facet |
time_zone | string | — | IANA time zone used by Spotify home personalization |
section_items_limit | integer | — | Per-section item limit, clamped to 1-50 |
include_episode_content_ratings_v2 | boolean | — | Include Spotify episode content ratings v2 |
Parameters from the server's own tool schema.
Why spotify_home is rated Low
Even though spotify_home 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
The rule that runs spotify_home safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spotify_home, this is the rule to start with:
spotify_home 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 Crawlora, apply this rule, and every spotify_home call is checked against it from then on.
Questions about spotify_home
Retrieve Spotify home sections. Returns normalized shelves and items from Spotify's Web Player home Pathfinder response. The endpoint fetches anonymous Spotify credentials at request time; caller-supplied Spotify bearer or client tokens are not required. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
spotify_home accepts 5 parameters: sp_t, facet, time_zone, section_items_limit, include_episode_content_ratings_v2. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for spotify_home: 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 Crawlora. Nothing to install.
spotify_home 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 spotify_home 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 spotify_home. 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.
spotify_home is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue