snapshot_disk_usage

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/snapshot-disk-usage.md

WHAT IT DOES

What snapshot_disk_usage does on Spotify

AI agents call snapshot_disk_usage 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 snapshot_disk_usage is rated Low

Tool retrieves and reports snapshot storage metrics with no data modification or side effects.

From the tool's definition Report disk usage, total size, file count, per-playlist breakdown, largest files

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs snapshot_disk_usage 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 snapshot_disk_usage, this is the rule to start with:

snapshot_disk_usage Allowed

snapshot_disk_usage 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": {
    "snapshot_disk_usage": {}
  }
}

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 snapshot_disk_usage call is checked against it from then on.

FAQ

Questions about snapshot_disk_usage

What does the snapshot_disk_usage tool do? +

Report disk usage of the snapshot directory: total size, file count, per-playlist breakdown, and the largest files Snapshot guide: take_playlist_snapshot (create), list_saved_snapshots (list), read_playlist_snapshot (read), diff_playlist_snapshots / snapshot_new_tracks / snapshot_removed_tracks (diff), restore_playlist_from_snapshot / restore_playlist_plan (restore). 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 snapshot_disk_usage? +

Register the Spotify MCP server in PolicyLayer and add a rule for snapshot_disk_usage: 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 snapshot_disk_usage? +

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

Can I rate-limit snapshot_disk_usage? +

Yes. Add a rate_limit block to the snapshot_disk_usage 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 snapshot_disk_usage completely? +

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

snapshot_disk_usage 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 538 Spotify tools →

Across the catalogue

The MCP Attack Database →

Guides

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