fw_pause
Pause the currently-playing audio stream on the glasses. Playback can be resumed with fw_resume.
This record as markdown: /tools/kh0pper-crow/fw-pause.md
What fw_pause does on Crow
AI agents invoke fw_pause 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_pause is rated High
This tool triggers an external operation (pausing audio playback on a hardware device). It is reversible (can be resumed), so not Destructive, and fits Execute as it controls an external device/operation. The blast radius is low — misuse only interrupts audio playback.
From the tool's definition Pause the currently-playing audio stream on the glasses. Playback can be resumed with fw_resume.
Attacks that exploit this kind of access
The rule that runs fw_pause 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_pause, this is the rule to start with:
fw_pause 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_pause call is checked against it from then on.
Questions about fw_pause
Pause the currently-playing audio stream on the glasses. Playback can be resumed with fw_resume. 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_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 Crow. Nothing to install.
fw_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 fw_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 fw_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.
fw_pause 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