mikrotik_remove_container

Removes a container

Server MikroTik Cursor MCP kevinpez/mikrotik-cursor-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What mikrotik_remove_container does on MikroTik Cursor MCP

AI agents call mikrotik_remove_container 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_container needs a policy

Removing a container is a destructive action that cannot be easily undone and will immediately cease operation of whatever service the container provides. This has potential for significant operational impact on network services. While not as critical as removing core routing configuration, it is irreversible and warrants the Destructive category over Execute, with high severity due to potential service disruption.

From the tool's definition Tool name explicitly states 'remove_container' and description 'Removes a container'. Container removal is an irreversible deletion of a containerized application or service running on the MikroTik router.

Questions about mikrotik_remove_container

What does the mikrotik_remove_container tool do? +

Removes a container. 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_container? +

Register the MikroTik Cursor MCP server in PolicyLayer and add a rule for mikrotik_remove_container: 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_container? +

mikrotik_remove_container 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_container? +

Yes. Add a rate_limit block to the mikrotik_remove_container 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_container completely? +

Set action: deny in the PolicyLayer policy for mikrotik_remove_container. 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_container? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.