This record as markdown: /tools/kh0pper-crow/fw-upload-track.md
What fw_upload_track does on Crow
AI agents use fw_upload_track to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
Why fw_upload_track is rated Medium
This tool creates or modifies data by uploading an audio file to a library. It is reversible (files can be deleted or replaced), so it falls under Write rather than Destructive.
From the tool's definition Tool name 'fw_upload_track' and description 'Upload an audio file to a library' indicate a create/modify operation that adds new data to a system.
Attacks that exploit this kind of access
The rule that runs fw_upload_track 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_upload_track, this is the rule to start with:
fw_upload_track stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_upload_track call is checked against it from then on.
Questions about fw_upload_track
Upload an audio file to a library. Pass. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for fw_upload_track: 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_upload_track is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the fw_upload_track 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_upload_track. 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_upload_track 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