mikrotik_set_container_registry · MikroTik Cursor MCP

WHAT IT DOES

What mikrotik_set_container_registry does on MikroTik Cursor MCP

AI agents use mikrotik_set_container_registry 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.

WHY IT NEEDS A POLICY

Why mikrotik_set_container_registry needs a policy

This tool modifies router configuration by setting container registry parameters. It is reversible (settings can be changed again), so it is Write rather than Destructive. Severity is high because misconfiguring container registries on network infrastructure could disrupt container deployment, introduce security vulnerabilities by pointing to untrusted registries, or cause service failures.

From the tool's definition Tool name 'mikrotik_set_container_registry' and description 'Sets container registry' indicate modification of router configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mikrotik_set_container_registry Rate-limited

mikrotik_set_container_registry stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mikrotik_set_container_registry": {
      "limits": [
        {
          "counter": "mikrotik_set_container_registry_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MikroTik Cursor MCP, so you can run agents against it safely.

FAQ

Questions about mikrotik_set_container_registry

What does the mikrotik_set_container_registry tool do? +

Sets container registry. 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.

How do I enforce a policy on mikrotik_set_container_registry? +

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

mikrotik_set_container_registry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mikrotik_set_container_registry? +

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

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

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