AI agents invoke metube_cancel_add to trigger actions in Metube. 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 cancels/aborts an in-progress operation (the add/queue operation). It is an active intervention that triggers an external state change on the MeTube instance — stopping a running process. It doesn't read data, write/create new data, delete existing data, or move money, but it does trigger an operational effect on a running process, making Execute the best fit.
From the tool's definition Cancel the current add operation (useful for large playlists)
Attacks that exploit this kind of access
Cancel the current add operation (useful for large playlists). It is categorised as a Execute tool in the Metube MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Metube MCP server in PolicyLayer and add a rule for metube_cancel_add: 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 Metube. Nothing to install.
metube_cancel_add 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 metube_cancel_add 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 metube_cancel_add. 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.
metube_cancel_add is provided by the Metube MCP server (junglem0nkey/metube-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 →