local_traceroute · Net MCP: Risk & Policy

WHAT IT DOES

What local_traceroute does on Net

AI agents invoke local_traceroute to trigger actions in Net. 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 local_traceroute needs a policy

Traceroute is a network diagnostic tool that executes an OS-level command to send packets and measure routes to a destination. Despite the empty description (which lowers confidence), the name strongly implies executing a local system command. This falls under Execute as it triggers an external operation. Misuse could be used to probe internal network topology, but blast radius is generally medium.

From the tool's definition Tool name 'local_traceroute' implies execution of a local network diagnostic command (traceroute), which runs a system-level process to probe network paths.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

local_traceroute Rate-limited

local_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": {
    "local_traceroute": {
      "limits": [
        {
          "counter": "local_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 Net, so you can run agents against it safely.

FAQ

Questions about local_traceroute

What does the local_traceroute tool do? +

local_traceroute. It is categorised as a Execute tool in the Net MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on local_traceroute? +

Register the Net MCP server in PolicyLayer and add a rule for local_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 Net. Nothing to install.

What risk level is local_traceroute? +

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

Can I rate-limit local_traceroute? +

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

Set action: deny in the PolicyLayer policy for local_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 local_traceroute? +

local_traceroute is provided by the Net MCP server (steelcutoatmeal/net-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.