Get keyword filter status including enabled state, number of rules, and schedule
AI agents call get_keyword_filter_status 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 configuration and status information about keyword filtering on the router. It performs a query operation that returns data (enabled state, rule count, schedule) without creating, modifying, deleting, or executing any actions. The verb 'get' and the passive nature of status retrieval are characteristic of Read category tools.
From the tool's definition Tool name 'get_keyword_filter_status' and description 'Get keyword filter status including enabled state, number of rules, and schedule' indicate purely informational retrieval with no state modification.
Documented attack patterns abuse exactly the kind of access get_keyword_filter_status 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_keyword_filter_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_keyword_filter_status": {}
}
}get_keyword_filter_status 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 keyword filter status including enabled state, number of rules, and schedule. 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_keyword_filter_status: 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_keyword_filter_status 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_keyword_filter_status 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_keyword_filter_status. 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_keyword_filter_status 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.