local_dig · Net MCP: Risk & Policy

WHAT IT DOES

What local_dig does on Net

AI agents invoke local_dig 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_dig needs a policy

The name implies running a local 'dig' command (a DNS diagnostic tool), which would constitute executing an external process. However, the empty description significantly reduces confidence. Given the server context (DNS queries, network diagnostics), this is likely a local DNS query executor.

From the tool's definition Tool name 'local_dig' suggests execution of the 'dig' DNS lookup utility locally; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

local_dig Rate-limited

local_dig 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_dig": {
      "limits": [
        {
          "counter": "local_dig_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_dig

What does the local_dig tool do? +

local_dig. 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_dig? +

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

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

Can I rate-limit local_dig? +

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

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

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