Upload an audio file to a library. Pass
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.
Uploading an audio file creates or adds new data to a library, which is a reversible Write operation. While it modifies state, it does not execute arbitrary code, delete data irreversibly, or have financial implications. The incomplete description ('Pass') suggests partial documentation, which slightly lowers confidence but does not change the core classification.
From the tool's definition Tool name 'fw_upload_track' and description 'Upload an audio file to a library' indicate a file creation/upload operation that modifies library state.
Documented attack patterns abuse exactly the kind of access fw_upload_track gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for fw_upload_track:
{
"version": "1",
"default": "deny",
"tools": {
"fw_upload_track": {
"limits": [
{
"counter": "fw_upload_track_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.