rubeus_golden · Rubeus MCP Server MCP: Risk & Policy

WHAT IT DOES

What rubeus_golden does on Rubeus MCP Server

AI agents invoke rubeus_golden 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_golden needs a policy

This tool forges Kerberos Golden Tickets using the krbtgt hash, which grants domain-wide persistent access by bypassing normal authentication. This is a critical offensive security/attack capability that executes Kerberos abuse operations. It doesn't merely read or write data — it actively executes a domain compromise technique.

From the tool's definition Forge a Golden Ticket (forged TGT with krbtgt hash)... bypasses normal authentication and can be used for persistent domain access

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rubeus_golden Rate-limited

rubeus_golden 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_golden": {
      "limits": [
        {
          "counter": "rubeus_golden_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_golden

What does the rubeus_golden tool do? +

Forge a Golden Ticket (forged TGT with krbtgt hash). Creates a TGT that grants domain-wide access. Requires: - Domain SID - krbtgt account hash (RC4 or AES) - Target username and domain The golden ticket bypasses normal authentication and can be used for persistent domain access. 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_golden? +

Register the Rubeus MCP Server MCP server in PolicyLayer and add a rule for rubeus_golden: 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_golden? +

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

Can I rate-limit rubeus_golden? +

Yes. Add a rate_limit block to the rubeus_golden 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_golden completely? +

Set action: deny in the PolicyLayer policy for rubeus_golden. 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_golden? +

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