This record as markdown: /tools/novalux12-spotify-mcp/get-me.md
What get_me does on Spotify
AI agents call get_me 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.
Why get_me is rated Low
This tool retrieves the authenticated user's information from Spotify. It is a read-only operation with no side effects, no data modification, no code execution, and no destructive capability. The blast radius if misused is minimal—an AI agent can only access the current user's profile data, which is already available through authentication context. Classified as Read with low severity.
From the tool's definition Tool name 'get_me' and description 'Get the current user' indicate a retrieval operation that queries user profile information without modifying or executing any actions.
Attacks that exploit this kind of access
The rule that runs get_me 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 get_me, this is the rule to start with:
get_me 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 Spotify, apply this rule, and every get_me call is checked against it from then on.
Questions about get_me
Get the current user. It is categorised as a Read tool in the Spotify MCP Server, which means it retrieves data without modifying state.
Register the Spotify MCP server in PolicyLayer and add a rule for get_me: 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.
get_me 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 get_me 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 get_me. 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.
get_me 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.
More on Spotify, and thousands of servers like it.
This server
Across the catalogue