fw_now_playing
Most recent listening activity for the authenticated user (last N listens).
This record as markdown: /tools/kh0pper-crow/fw-now-playing.md
What fw_now_playing does on Crow
AI agents call fw_now_playing to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why fw_now_playing is rated Low
This tool only retrieves historical listening activity data for the authenticated user. It performs a read-only query with no side effects, no data modification, no code execution, and no destructive operations. The severity is low because the data retrieved is limited to the user's own listening history, which has minimal blast radius even if misused by an AI agent.
From the tool's definition Tool description states it retrieves 'most recent listening activity for the authenticated user (last N listens)' - a query operation with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs fw_now_playing 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_now_playing, this is the rule to start with:
fw_now_playing is read-only, so it stays allowed. 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_now_playing call is checked against it from then on.
Questions about fw_now_playing
Most recent listening activity for the authenticated user (last N listens). It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for fw_now_playing: 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_now_playing is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fw_now_playing 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_now_playing. 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_now_playing 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