AI agents call openwrt_opkg_remove to permanently remove resources in OpenWRT SSH MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Package removal is an irreversible operation that cannot be undone by the tool itself and may render the router non-functional if critical packages are removed. While Write tools create or modify reversibly, Destructive tools permanently remove or delete data/functionality. This exceeds Write severity due to the inability to undo the action and potential to break system functionality.
From the tool's definition Tool name is 'openwrt_opkg_remove' and description states 'Remove a package using opkg'. The opkg remove command irreversibly deletes software packages from the router system, potentially disabling critical network services and creating an unrecoverable state…
Documented attack patterns abuse exactly the kind of access openwrt_opkg_remove 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_opkg_remove:
{
"version": "1",
"default": "deny",
"hide": [
"openwrt_opkg_remove"
]
} openwrt_opkg_remove disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a package using opkg. It is categorised as a Destructive tool in the OpenWRT SSH MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OpenWRT SSH MCP Server MCP server in PolicyLayer and add a rule for openwrt_opkg_remove: 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_opkg_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the openwrt_opkg_remove 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_opkg_remove. 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_opkg_remove 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.