Low Risk

get_connected_devices

List all devices connected to the router (via DHCP)

How to control get_connected_devices ↓

What get_connected_devices does on ASUS Merlin Router MCP Server

AI agents call get_connected_devices to retrieve information from ASUS Merlin Router MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_connected_devices needs a policy

This tool performs a read-only operation that lists connected devices. It retrieves existing data via DHCP status queries with no side effects, no data modification, and no destructive actions. While the information could be sensitive in some contexts, the tool itself is purely informational.

From the tool's definition Tool name 'get_connected_devices' and description 'List all devices connected to the router (via DHCP)' indicate a query operation that retrieves information without modifying state.

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

How to control get_connected_devices

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_connected_devices": {}
  }
}

get_connected_devices is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_connected_devices

What does the get_connected_devices tool do? +

List all devices connected to the router (via DHCP). 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_connected_devices? +

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

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

Can I rate-limit get_connected_devices? +

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

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

get_connected_devices 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.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.