AI agents invoke dnscat_client 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.
dnscat_client would establish DNS-based tunnels for command execution and data exfiltration—core Execute capabilities. While the description is empty, the tool name combined with server context and sibling tools strongly indicates this performs active network operations (tunneling, C2 communication) whose effects are contingent on attacker-supplied arguments.
From the tool's definition Tool name 'dnscat_client' references dnscat, a DNS tunneling tool commonly used in penetration testing to establish covert command-and-control channels.
Documented attack patterns abuse exactly the kind of access dnscat_client gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pentester-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for dnscat_client:
{
"version": "1",
"default": "deny",
"tools": {
"dnscat_client": {
"limits": [
{
"counter": "dnscat_client_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}dnscat_client 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.
dnscat_client. 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.
Register the Pentester- MCP server in PolicyLayer and add a rule for dnscat_client: 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.
dnscat_client 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 dnscat_client 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 dnscat_client. 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.
dnscat_client 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.
Start from Pentester-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
337 Pentester-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.