Execute a custom command on the router via SSH. WARNING: NEVER use this for file operations (reading, writing, editing files). ALWAYS use read_file, upload_file, or download_file tools for file operations. Do NOT use heredoc (cat << EOF) or echo for file writes - use upload_file instead.
AI agents invoke execute_command to trigger actions in ASUS Merlin Router MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool allows execution of arbitrary commands on a router device via SSH. While the description warns against using it for file operations (suggesting some guardrails exist), the core functionality remains unrestricted command execution on a network device.
From the tool's definition Tool name is 'execute_command' and description states 'Execute a custom command on the router via SSH.' The SSH access to a network device with custom command execution capability creates arbitrary code execution potential.
Documented attack patterns abuse exactly the kind of access execute_command gives an agent:
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 execute_command:
{
"version": "1",
"default": "deny",
"tools": {
"execute_command": {
"limits": [
{
"counter": "execute_command_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_command 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.
Free to start. No card required.
Execute a custom command on the router via SSH. WARNING: NEVER use this for file operations (reading, writing, editing files). ALWAYS use read_file, upload_file, or download_file tools for file operations. Do NOT use heredoc (cat << EOF) or echo for file writes - use upload_file instead. 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.
Register the ASUS Merlin Router MCP Server MCP server in PolicyLayer and add a rule for execute_command: 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.
execute_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_command 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 execute_command. 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.
execute_command 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.
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.
Free to start. No card required.
47 ASUS Merlin Router MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.