Lists static DNS entries
AI agents call mikrotik_list_dns_static to retrieve information from MikroTik Cursor MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves DNS configuration from a MikroTik router. It queries existing data and performs no modifications, deletions, code execution, or financial operations. Even in a broader context where other sibling tools can modify router configuration, this specific tool is purely informational. Misuse would expose DNS settings but cannot directly damage infrastructure or trigger unintended network changes.
From the tool's definition Tool name 'mikrotik_list_dns_static' and description 'Lists static DNS entries' indicate a retrieval operation with no modification. The verb 'list' and the passive phrase 'lists...entries' denote querying existing data without side effects.
Attacks that exploit this kind of access
Lists static DNS entries. It is categorised as a Read tool in the MikroTik Cursor MCP MCP Server, which means it retrieves data without modifying state.
Register the MikroTik Cursor MCP server in PolicyLayer and add a rule for mikrotik_list_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_list_dns_static is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mikrotik_list_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_list_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_list_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 →