This record as markdown: /tools/nyxstrike/dig-dns.md
What dig_dns does on Nyxstrike
AI agents call dig_dns to retrieve information from Nyxstrike without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why dig_dns is rated Low
The tool name 'dig_dns' strongly implies it wraps the standard 'dig' DNS query utility, which retrieves DNS records without side effects. However, on an offensive security/penetration testing platform like Nyxstrike, DNS tools can be used for reconnaissance, zone transfers, or DNS enumeration. The empty description lowers confidence.
From the tool's definition Tool name 'dig_dns' suggests DNS lookup/query operations, which are read-only reconnaissance activities. Description is empty, lowering confidence.
Attacks that exploit this kind of access
The rule that runs dig_dns safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nyxstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dig_dns, this is the rule to start with:
dig_dns is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nyxstrike, apply this rule, and every dig_dns call is checked against it from then on.
Questions about dig_dns
dig_dns is a read tool on the Nyxstrike MCP server. It is categorised as a Read tool in the Nyxstrike MCP Server, which means it retrieves data without modifying state.
Register the Nyxstrike MCP server in PolicyLayer and add a rule for dig_dns: 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 Nyxstrike. Nothing to install.
dig_dns is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the dig_dns 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 dig_dns. 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.
dig_dns is provided by the Nyxstrike MCP server (CommonHuman-Lab/nyxstrike). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nyxstrike, and thousands of servers like it.
This server
Across the catalogue