mikrotik_traceroute · MikroTik Cursor MCP: Risk & Policy

WHAT IT DOES

What mikrotik_traceroute does on MikroTik Cursor MCP

AI agents invoke mikrotik_traceroute to trigger actions in MikroTik Cursor MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why mikrotik_traceroute needs a policy

Traceroute is a network diagnostic command that actively sends probe packets from the router to a target host, triggering real network operations. It is not a passive read/query of stored data — it executes a live network operation. While it has no persistent side effects, it does generate network traffic and consumes router resources, placing it in the Execute category.

From the tool's definition Traceroute to a host from the MikroTik router

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mikrotik_traceroute Rate-limited

mikrotik_traceroute stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_traceroute": {
      "limits": [
        {
          "counter": "mikrotik_traceroute_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_traceroute

What does the mikrotik_traceroute tool do? +

Traceroute to a host from the MikroTik router. It is categorised as a Execute tool in the MikroTik Cursor MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mikrotik_traceroute? +

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

mikrotik_traceroute is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit mikrotik_traceroute? +

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

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

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