New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

mikrotik_remove_ipv6_pool

Removes an IPv6 pool

SERVERMikroTik Cursor MCP SOURCEkevinpez/mikrotik-cursor-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kevinpez-mikrotik-cursor-mcp/mikrotik-remove-ipv6-pool.md

What mikrotik_remove_ipv6_pool does on MikroTik Cursor MCP

AI agents call mikrotik_remove_ipv6_pool to permanently remove resources in MikroTik Cursor MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why mikrotik_remove_ipv6_pool is rated Critical

Removing an IPv6 pool is an irreversible destructive action that deletes network resource allocation configuration. Once removed, the pool cannot be recovered without manual reconfiguration. This affects network connectivity for devices relying on that pool. The action cannot be undone automatically, placing it in the Destructive category rather than Write.

From the tool's definition Tool name 'mikrotik_remove_ipv6_pool' and description 'Removes an IPv6 pool' indicate deletion of network configuration data.

Questions about mikrotik_remove_ipv6_pool

What does the mikrotik_remove_ipv6_pool tool do? +

Removes an IPv6 pool. It is categorised as a Destructive tool in the MikroTik Cursor MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on mikrotik_remove_ipv6_pool? +

Register the MikroTik Cursor MCP server in PolicyLayer and add a rule for mikrotik_remove_ipv6_pool: 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.

What risk level is mikrotik_remove_ipv6_pool? +

mikrotik_remove_ipv6_pool is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit mikrotik_remove_ipv6_pool? +

Yes. Add a rate_limit block to the mikrotik_remove_ipv6_pool 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.

How do I block mikrotik_remove_ipv6_pool completely? +

Set action: deny in the PolicyLayer policy for mikrotik_remove_ipv6_pool. 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.

What MCP server provides mikrotik_remove_ipv6_pool? +

mikrotik_remove_ipv6_pool 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.

More on MikroTik Cursor, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of MikroTik Cursor's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.