Critical Risk →

remove_url_filter

Remove URL pattern from global filter list

How to control remove_url_filter ↓

What remove_url_filter does on ASUS Merlin Router MCP Server

AI agents call remove_url_filter to permanently remove resources in ASUS Merlin Router MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why remove_url_filter needs a policy

Removing a URL filter entry deletes a security policy rule. This is a destructive operation (irreversible deletion of a configuration entry) that affects network-level content filtering for all devices on the router. Misuse could expose users to previously blocked malicious URLs or content.

From the tool's definition 'Remove URL pattern from global filter list' — removal of a filter rule is irreversible without a prior backup and modifies security/access-control configuration permanently

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

How to control remove_url_filter

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_url_filter"
  ]
}

remove_url_filter disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  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.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about remove_url_filter

What does the remove_url_filter tool do? +

Remove URL pattern from global filter list. It is categorised as a Destructive tool in the ASUS Merlin Router MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_url_filter? +

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

remove_url_filter is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_url_filter? +

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

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

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