Run a dig command against the given domain with the provided options.
AI agents invoke run_dig_tool to trigger actions in pentestMCP. 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.
While dig itself is a read-only DNS reconnaissance tool that retrieves DNS records, it is invoked via the 'run_dig_tool' which executes commands with user-supplied arguments.
From the tool's definition Tool name 'run_dig_tool' and description 'Run a dig command against the given domain with the provided options' explicitly indicates execution of the dig DNS query utility. The verb 'Run' combined with 'dig command' demonstrates this is command execution.
Documented attack patterns abuse exactly the kind of access run_dig_tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and pentestMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for run_dig_tool:
{
"version": "1",
"default": "deny",
"tools": {
"run_dig_tool": {
"limits": [
{
"counter": "run_dig_tool_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_dig_tool 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.
Free to start. No card required.
Run a dig command against the given domain with the provided options. It is categorised as a Execute tool in the pentestMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the pentest MCP server in PolicyLayer and add a rule for run_dig_tool: 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 pentestMCP. Nothing to install.
run_dig_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_dig_tool 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.
Set action: deny in the PolicyLayer policy for run_dig_tool. 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.
run_dig_tool is provided by the pentest MCP server (ramkansal/pentestmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 pentestMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 pentestMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.