rubeus_diamond · Rubeus MCP Server MCP: Risk & Policy

WHAT IT DOES

What rubeus_diamond does on Rubeus MCP Server

AI agents invoke rubeus_diamond 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_diamond needs a policy

This tool forges Kerberos Diamond Tickets by requesting a legitimate TGT and modifying its PAC data, which constitutes a privilege escalation/credential forgery attack on Windows Active Directory. It executes complex Kerberos abuse operations that grant unauthorized access to domain resources.

From the tool's definition 'Forge a Diamond Ticket (modified legitimate TGT)' and 'modifies it with new PAC data' using 'krbtgt key for re-signing' — part of a Kerberos abuse MCP server

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rubeus_diamond Rate-limited

rubeus_diamond 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_diamond": {
      "limits": [
        {
          "counter": "rubeus_diamond_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_diamond

What does the rubeus_diamond tool do? +

Forge a Diamond Ticket (modified legitimate TGT). Requests a legitimate TGT and then modifies it with new PAC data. More stealthy than golden tickets as it starts with a real ticket. Requires krbtgt key for re-signing. 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_diamond? +

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

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

Can I rate-limit rubeus_diamond? +

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

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

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