AI agents invoke ad_responder_poison 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.
Responder is a network poisoning tool that actively intercepts and redirects network traffic by responding to broadcast name resolution queries, capturing NTLM hashes and credentials. This is an active attack execution that affects network-level operations and can compromise credentials across an entire network segment.
From the tool's definition Tool name 'ad_responder_poison' on a penetration testing MCP server alongside tools like ad_dcsync, ad_coerce_petitpotam, and ad_password_spray.
Documented attack patterns abuse exactly the kind of access ad_responder_poison 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 ad_responder_poison:
{
"version": "1",
"default": "deny",
"tools": {
"ad_responder_poison": {
"limits": [
{
"counter": "ad_responder_poison_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ad_responder_poison 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.
ad_responder_poison. 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 ad_responder_poison: 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.
ad_responder_poison 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 ad_responder_poison 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 ad_responder_poison. 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.
ad_responder_poison 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.