rubeus_kerberoast · Rubeus MCP Server MCP: Risk & Policy

WHAT IT DOES

What rubeus_kerberoast does on Rubeus MCP Server

AI agents invoke rubeus_kerberoast to trigger actions in Rubeus MCP Server. 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.

WHY IT NEEDS A POLICY

Why rubeus_kerberoast needs a policy

Kerberoasting is an active credential-harvesting attack against Active Directory. It requests Kerberos service tickets (TGS) for accounts with Service Principal Names (SPNs) and extracts the encrypted hashes for offline cracking. This is an offensive security operation that triggers external Kerberos interactions and can lead to domain-wide compromise if service account hashes are cracked.

From the tool's definition 'Perform Kerberoasting attack to extract service account password hashes. Requests TGS tickets for accounts with SPNs, which are encrypted with the service account'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rubeus_kerberoast Rate-limited

rubeus_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rubeus_kerberoast": {
      "limits": [
        {
          "counter": "rubeus_kerberoast_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Rubeus MCP Server, so you can run agents against it safely.

FAQ

Questions about rubeus_kerberoast

What does the rubeus_kerberoast tool do? +

Perform Kerberoasting attack to extract service account password hashes. Requests TGS tickets for accounts with SPNs, which are encrypted with the service account. It is categorised as a Execute tool in the Rubeus MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on rubeus_kerberoast? +

Register the Rubeus MCP Server MCP server in PolicyLayer and add a rule for rubeus_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 Rubeus MCP Server. Nothing to install.

What risk level is rubeus_kerberoast? +

rubeus_kerberoast is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit rubeus_kerberoast? +

Yes. Add a rate_limit block to the rubeus_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.

How do I block rubeus_kerberoast completely? +

Set action: deny in the PolicyLayer policy for rubeus_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.

What MCP server provides rubeus_kerberoast? +

rubeus_kerberoast is provided by the Rubeus MCP Server MCP server (schwarztim/sec-rubeus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.