mikrotik_update_dns_static · MikroTik MCP: Risk & Policy

WHAT IT DOES

What mikrotik_update_dns_static does on MikroTik MCP

AI agents use mikrotik_update_dns_static to create or update resources in MikroTik MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MikroTik MCP environment.

WHY IT NEEDS A POLICY

Why mikrotik_update_dns_static needs a policy

This tool modifies (updates) DNS configuration reversibly. It does not execute arbitrary commands, delete data, or move money. The severity is medium because DNS misconfiguration can disrupt network services, but the impact is limited to DNS resolution and is reversible—a standard write operation on network configuration. Confidence is high due to clear naming and description.

From the tool's definition Tool name contains 'update' and description states 'Updates an existing static DNS entry', indicating modification of DNS configuration data without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mikrotik_update_dns_static Rate-limited

mikrotik_update_dns_static stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mikrotik_update_dns_static": {
      "limits": [
        {
          "counter": "mikrotik_update_dns_static_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MikroTik MCP, so you can run agents against it safely.

FAQ

Questions about mikrotik_update_dns_static

What does the mikrotik_update_dns_static tool do? +

Updates an existing static DNS entry. It is categorised as a Write tool in the MikroTik MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mikrotik_update_dns_static? +

Register the MikroTik MCP server in PolicyLayer and add a rule for mikrotik_update_dns_static: 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 MikroTik MCP. Nothing to install.

What risk level is mikrotik_update_dns_static? +

mikrotik_update_dns_static is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mikrotik_update_dns_static? +

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

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

mikrotik_update_dns_static is provided by the MikroTik MCP server (tarcisiodier/mcp-mikrotik). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.