AI agents invoke spotify_pause to trigger actions in Kef. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation (pausing Spotify playback) on a connected speaker system. It has a side effect on an external service/device state, making it Execute rather than Write, though the impact is minimal and easily reversible.
From the tool's definition Pause Spotify playback
Attacks that exploit this kind of access
Pause Spotify playback. It is categorised as a Execute tool in the Kef MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kef MCP server in PolicyLayer and add a rule for spotify_pause: 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 Kef. Nothing to install.
spotify_pause is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the spotify_pause 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_pause. 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_pause is provided by the Kef MCP server (nqrwhal/kef-mcp). 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 →