mikrotik_create_container_env · MikroTik Cursor MCP

WHAT IT DOES

What mikrotik_create_container_env does on MikroTik Cursor MCP

AI agents use mikrotik_create_container_env 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_create_container_env needs a policy

The tool creates (writes) configuration data in a container environment. While the blast radius is limited to a single container's environment scope and the action is reversible, misuse could inject malicious environment variables that affect container behavior, secrets exposure, or application configuration poisoning.

From the tool's definition Tool name and description indicate it 'Creates container environment variable' – a direct data modification operation that adds or sets a new environment variable in a container context. This is reversible via update/delete operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mikrotik_create_container_env Rate-limited

mikrotik_create_container_env 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_create_container_env": {
      "limits": [
        {
          "counter": "mikrotik_create_container_env_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_create_container_env

What does the mikrotik_create_container_env tool do? +

Creates container environment variable. 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_create_container_env? +

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

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

Can I rate-limit mikrotik_create_container_env? +

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

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

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