Stop playing music
AI agents invoke stop_music to trigger actions in AutoBot MCP. 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.
While 'stop_music' appears simple, it is an Execute category tool because it triggers an external operation on a controlled device whose effects depend on the current system state. It is not Read (no data retrieval), Write (not creating/modifying persistent data), Destructive (reversible action), Financial, or Other.
From the tool's definition Tool executes a control action on an Android device via the AutoBot API that triggers an external operation (stopping music playback).
Attacks that exploit this kind of access
Stop playing music. It is categorised as a Execute tool in the AutoBot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AutoBot MCP server in PolicyLayer and add a rule for stop_music: 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 AutoBot MCP. Nothing to install.
stop_music 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 stop_music 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 stop_music. 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.
stop_music is provided by the AutoBot MCP server (yz0903/autobot-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 →