AI agents invoke run_coercer 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.
Coercer is a penetration testing tool that performs credential relay and coercion attacks by interacting with network services and Windows protocols (NTLM relay, SpoolSvc abuse, etc.). This triggers external operations with effects dependent on target arguments (which service, which credentials to coerce), making it Execute category.
From the tool's definition Tool named 'run_coercer' from a penetration testing MCP server that enables autonomous execution of 'open-source penetration testing tools' including 'web exploitation' via Docker sandboxing. Coercer is a known credential coercion/relay attack tool.
Documented attack patterns abuse exactly the kind of access run_coercer 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 run_coercer:
{
"version": "1",
"default": "deny",
"tools": {
"run_coercer": {
"limits": [
{
"counter": "run_coercer_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_coercer 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_coercer. 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 run_coercer: 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.
run_coercer 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_coercer 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_coercer. 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_coercer 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.