get_router_info

THE RISK

Low Risk

Why get_router_info needs a policy

This tool retrieves read-only system metrics and status information from the router. It has no side effects, does not modify any state, does not execute commands, and does not access or modify user data. The information gathered (uptime, memory usage, CPU stats, firmware version) are diagnostic metrics typically used for monitoring. No destructive, financial, or execution risk is present.

From the tool's definition Tool description explicitly states 'Get router system information (uptime, memory, CPU, firmware version)' - purely informational queries with no modification or execution capabilities.

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

POLICY

How to control get_router_info

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 get_router_info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_router_info": {}
  }
}

get_router_info is read-only, so it stays allowed — but 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.

CAP 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 →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_router_info

What does the get_router_info tool do? +

Get router system information (uptime, memory, CPU, firmware version). It is categorised as a Read tool in the ASUS Merlin Router MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_router_info? +

Register the ASUS Merlin Router MCP Server MCP server in PolicyLayer and add a rule for get_router_info: 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 get_router_info? +

get_router_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_router_info? +

Yes. Add a rate_limit block to the get_router_info 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 get_router_info completely? +

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

get_router_info 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 →