Removes a static DNS entry
AI agents call mikrotik_remove_dns_static to permanently remove resources in MikroTik MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a static DNS entry is an irreversible deletion operation. DNS entries are critical network infrastructure components; removing one can cause name resolution failures, service outages, or redirect traffic incorrectly. This is a destructive action with potentially wide blast radius on network-dependent services.
From the tool's definition Removes a static DNS entry
Attacks that exploit this kind of access
Removes a static DNS entry. It is categorised as a Destructive tool in the MikroTik MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MikroTik MCP server in PolicyLayer and add a rule for mikrotik_remove_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_remove_dns_static is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the mikrotik_remove_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_remove_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_remove_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 →