Upload a firmware image (.img or .bin) from the local machine to the router
AI agents use openwrt_firmware_upload to create or update resources in OpenWRT SSH MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenWRT SSH MCP Server environment.
This tool transfers a firmware image file to the router, which is a reversible write operation (the uploaded file can be deleted or overwritten). It does not execute or apply the firmware (that is openwrt_firmware_flash). However, the blast radius is high because uploading malicious firmware could enable complete router compromise.
From the tool's definition Tool name contains 'upload' and description states 'Upload a firmware image (.img or .bin) from the local machine to the router' — this creates/transfers a file to the target system.
Documented attack patterns abuse exactly the kind of access openwrt_firmware_upload gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenWRT SSH MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for openwrt_firmware_upload:
{
"version": "1",
"default": "deny",
"tools": {
"openwrt_firmware_upload": {
"limits": [
{
"counter": "openwrt_firmware_upload_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}openwrt_firmware_upload 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 a firmware image (.img or .bin) from the local machine to the router. It is categorised as a Write tool in the OpenWRT SSH MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenWRT SSH MCP Server MCP server in PolicyLayer and add a rule for openwrt_firmware_upload: 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 OpenWRT SSH MCP Server. Nothing to install.
openwrt_firmware_upload 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 openwrt_firmware_upload 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 openwrt_firmware_upload. 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.
openwrt_firmware_upload is provided by the OpenWRT SSH MCP Server MCP server (jsebgiraldo/openwrt_ssh_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenWRT SSH MCP Server, 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.
23 OpenWRT SSH MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.