AI agents invoke cast_resume 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 on a physical device (KEF speaker) — resuming Cast playback. It has a real-world side effect (audio starts playing) but is reversible and low-blast-radius. It fits Execute as it triggers an external operation rather than simply reading or writing data.
From the tool's definition Resume paused Cast playback on the KEF
Attacks that exploit this kind of access
Resume paused Cast playback on the KEF. 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 cast_resume: 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.
cast_resume 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 cast_resume 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 cast_resume. 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.
cast_resume 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 →