local_mtr · Net MCP: Risk & Policy

WHAT IT DOES

What local_mtr does on Net

AI agents invoke local_mtr 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_mtr needs a policy

MTR is a network diagnostic tool that combines traceroute and ping by executing system-level commands. Based on the name and the server context (network engineering diagnostics), this tool likely runs a local MTR command, which constitutes executing an external operation. However, the empty description significantly lowers confidence.

From the tool's definition Tool name 'local_mtr' suggests running a local MTR (My Traceroute) network diagnostic command, but the description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

local_mtr Rate-limited

local_mtr 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_mtr": {
      "limits": [
        {
          "counter": "local_mtr_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_mtr

What does the local_mtr tool do? +

local_mtr. 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_mtr? +

Register the Net MCP server in PolicyLayer and add a rule for local_mtr: 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_mtr? +

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

Can I rate-limit local_mtr? +

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

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

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