Enables a static DNS entry
AI agents use mikrotik_enable_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.
This tool modifies network configuration (DNS settings) in a reversible manner—enabling a static DNS entry can be disabled/undone. It does not delete data, execute arbitrary code, move money, or trigger irreversible changes. The blast radius is medium because DNS misconfigurations can disrupt network services for users relying on the router, but the change is reversible.
From the tool's definition Tool name 'mikrotik_enable_dns_static' and description 'Enables a static DNS entry' indicate modification of DNS configuration settings on a MikroTik RouterOS device.
Attacks that exploit this kind of access
Enables a 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.
Register the MikroTik MCP server in PolicyLayer and add a rule for mikrotik_enable_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.
mikrotik_enable_dns_static is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mikrotik_enable_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.
Set action: deny in the PolicyLayer policy for mikrotik_enable_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.
mikrotik_enable_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →