run_dig

A execute tool on the Pentester- MCP server.

SERVERPentester-MCP SOURCEhalilkirazkaya/pentester-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/halilkirazkaya-pentester-mcp/run-dig.md

WHAT IT DOES

What run_dig does on Pentester-MCP

AI agents invoke run_dig to trigger actions in Pentester-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.

RISK

Why run_dig is rated High

The tool name 'run_dig' strongly suggests execution of the 'dig' DNS lookup utility, a common reconnaissance tool. The server context explicitly describes autonomous execution of penetration testing tools including reconnaissance. While 'dig' itself is typically a read/query operation, on this pentesting platform it is executed as an active tool with potentially sensitive DNS enumeration capabilities.

From the tool's definition Tool name 'run_dig' on a penetration testing server that 'autonomously execute over 200 open-source penetration testing tools' including 'reconnaissance'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_dig safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pentester-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_dig, this is the rule to start with:

run_dig Rate-limited

run_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": {
    "run_dig": {
      "limits": [
        {
          "counter": "run_dig_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pentester-MCP, apply this rule, and every run_dig call is checked against it from then on.

FAQ

Questions about run_dig

What does the run_dig tool do? +

run_dig is a execute tool on the Pentester MCP server. It is categorised as a Execute tool in the Pentester-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 run_dig? +

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

What risk level is run_dig? +

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

Can I rate-limit run_dig? +

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

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

run_dig is provided by the Pentester MCP server (halilkirazkaya/pentester-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pentester, and thousands of servers like it.

This server

All 337 Pentester tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →