fw_play
Play a Funkwhale track on the paired glasses / phone speaker. Takes a track UUID from fw_search. Returns a streaming envelope that the meta-glasses voice loop intercepts; the LLM should summarize verbally (e.g.
This record as markdown: /tools/kh0pper-crow/fw-play.md
What fw_play does on Crow
AI agents invoke fw_play to trigger actions in Crow. 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.
Why fw_play is rated High
This tool triggers an external operation — playing audio on a physical device (glasses/phone speaker). It executes a media playback action with real-world effects on hardware, making it an Execute category tool. Misuse could cause unwanted audio playback on paired devices, hence medium severity.
From the tool's definition Play a Funkwhale track on the paired glasses / phone speaker... Returns a streaming envelope that the meta-glasses voice loop intercepts
Attacks that exploit this kind of access
The rule that runs fw_play safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fw_play, this is the rule to start with:
fw_play stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every fw_play call is checked against it from then on.
Questions about fw_play
Play a Funkwhale track on the paired glasses / phone speaker. Takes a track UUID from fw_search. Returns a streaming envelope that the meta-glasses voice loop intercepts; the LLM should summarize verbally (e.g. It is categorised as a Execute tool in the Crow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Crow MCP server in PolicyLayer and add a rule for fw_play: 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 Crow. Nothing to install.
fw_play 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 fw_play 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 fw_play. 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.
fw_play is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue