Adds a static DNS entry
AI agents use mikrotik_add_dns_static to create or update resources in MikroTik Cursor MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MikroTik Cursor MCP environment.
This tool creates or modifies DNS configuration on a MikroTik router by adding static DNS entries. This is a Write operation because it creates new data reversibly. Severity is medium because misconfigured DNS entries can disrupt network services or be used to redirect traffic maliciously, but the effect is limited to DNS resolution on that router and is reversible.
From the tool's definition Tool name is 'mikrotik_add_dns_static' with description 'Adds a static DNS entry'. The verb 'add' indicates creation of new data (a DNS record) which is reversible via deletion.
Attacks that exploit this kind of access
Adds a static DNS entry. It is categorised as a Write tool in the MikroTik Cursor MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MikroTik Cursor MCP server in PolicyLayer and add a rule for mikrotik_add_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 Cursor MCP. Nothing to install.
mikrotik_add_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_add_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_add_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_add_dns_static is provided by the MikroTik Cursor MCP server (kevinpez/mikrotik-cursor-mcp). 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 →