Get system log entries from the router with optional filtering
AI agents call get_system_log 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 log entries for monitoring/diagnostic purposes. It has no side effects—it only reads existing system logs. The optional filtering is a read-time parameter that does not alter data. While the ASUS Merlin server includes execute and destructive tools like execute_command and add_url_filter, this specific tool is purely informational.
From the tool's definition Tool name 'get_system_log' and description 'Get system log entries from the router with optional filtering' indicate retrieval of existing log data without modification or execution of commands.
Documented attack patterns abuse exactly the kind of access get_system_log 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 get_system_log:
{
"version": "1",
"default": "deny",
"tools": {
"get_system_log": {}
}
}get_system_log 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.
Get system log entries from the router with optional filtering. 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 get_system_log: 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.
get_system_log 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 get_system_log 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 get_system_log. 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.
get_system_log 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.