set_nvram_variable

THE RISK

High Risk

Why set_nvram_variable needs a policy

Writing NVRAM variables directly modifies persistent low-level router firmware configuration. Incorrect values can render the router inoperable or misconfigured in ways that are difficult to reverse, and this is executed at the firmware level via SSH.

From the tool's definition 'Set a NVRAM variable value. WARNING: Incorrect values can break router configuration.'

Documented attack patterns abuse exactly the kind of access set_nvram_variable gives an agent:

POLICY

How to control set_nvram_variable

PolicyLayer is an MCP gateway — it sits between your AI agents and ASUS Merlin Router MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for set_nvram_variable:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_nvram_variable": {
      "limits": [
        {
          "counter": "set_nvram_variable_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

set_nvram_variable stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register ASUS Merlin Router MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More ASUS Merlin Router MCP Server tools

Destructive remove_dhcp_reservation Remove DHCP reservation by MAC or IP address Destructive remove_keyword_filter Remove keyword from filter list Destructive remove_mac_filter Remove device from MAC filter Destructive remove_network_service_filter_rule Remove network service filter rule by matching all criteria exactly Destructive remove_url_filter Remove URL pattern from global filter list Destructive remove_vpn_routing_policy Remove device from VPN Director routing (Asuswrt-Merlin firmware only). Device will return Execute execute_command Execute a custom command on the router via SSH. WARNING: NEVER use this for file operation Execute restart_service Restart a specific router service (e.g., wireless, vpnclient1, httpd)

All 47 ASUS Merlin Router MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in ASUS Merlin Router MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about set_nvram_variable

What does the set_nvram_variable tool do? +

Set a NVRAM variable value. WARNING: Incorrect values can break router configuration. It is categorised as a Execute tool in the ASUS Merlin Router MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on set_nvram_variable? +

Register the ASUS Merlin Router MCP Server MCP server in PolicyLayer and add a rule for set_nvram_variable: 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 ASUS Merlin Router MCP Server. Nothing to install.

What risk level is set_nvram_variable? +

set_nvram_variable is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit set_nvram_variable? +

Yes. Add a rate_limit block to the set_nvram_variable 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.

How do I block set_nvram_variable completely? +

Set action: deny in the PolicyLayer policy for set_nvram_variable. 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.

What MCP server provides set_nvram_variable? +

set_nvram_variable is provided by the ASUS Merlin Router MCP Server MCP server (kcsoukup/asus-merlin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ASUS Merlin Router MCP Server tool call.

Start from ASUS Merlin Router MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →