Gets DHCPv6 server details
AI agents call mikrotik_get_dhcpv6_server 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 queries and retrieves DHCPv6 server configuration or status information from a MikroTik router. It has no side effects, does not create, modify, delete, or execute commands that alter router state. The 'get' verb and 'details' retrieval semantics confirm it is a Read operation. Severity is low because reading router configuration poses minimal risk in isolation.
From the tool's definition Tool name contains 'get' and description states 'Gets DHCPv6 server details' — a retrieval operation with no modification capability.
Attacks that exploit this kind of access
Gets DHCPv6 server details. 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_get_dhcpv6_server: 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_get_dhcpv6_server 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_get_dhcpv6_server 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_get_dhcpv6_server. 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_get_dhcpv6_server 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 →