List running processes on the router
AI agents call list_processes 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.
This tool retrieves information about running processes on the router. It performs no side effects, creates no changes, executes no commands, and does not delete or move resources. It is a straightforward read operation analogous to 'ps' or 'top' commands. While the server as a whole supports destructive operations (e.g., execute_command), this specific tool is limited to process enumeration.
From the tool's definition Tool name 'list_processes' and description 'List running processes on the router' indicate a query operation that retrieves system state without modification.
Documented attack patterns abuse exactly the kind of access list_processes 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 list_processes:
{
"version": "1",
"default": "deny",
"tools": {
"list_processes": {}
}
} list_processes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List running processes on the router. It is categorised as a Read tool in the ASUS Merlin Router MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ASUS Merlin Router MCP Server MCP server in PolicyLayer and add a rule for list_processes: 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.
list_processes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_processes 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 list_processes. 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.
list_processes 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.