AI agents invoke ad_kerberoast 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.
Kerberoasting is a well-known Active Directory credential theft technique that requests TGS tickets for service accounts and attempts offline brute-force of their passwords. Even with an empty description, the tool name is unambiguous in context of this penetration testing server.
From the tool's definition Tool name 'ad_kerberoast' on a penetration testing MCP server alongside tools like ad_dcsync, ad_password_spray, ad_coerce_petitpotam.
Documented attack patterns abuse exactly the kind of access ad_kerberoast 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_kerberoast:
{
"version": "1",
"default": "deny",
"tools": {
"ad_kerberoast": {
"limits": [
{
"counter": "ad_kerberoast_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ad_kerberoast 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_kerberoast. 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_kerberoast: 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_kerberoast 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_kerberoast 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_kerberoast. 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_kerberoast 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.