rubeus_tgtdeleg · Rubeus MCP Server MCP: Risk & Policy

WHAT IT DOES

What rubeus_tgtdeleg does on Rubeus MCP Server

AI agents invoke rubeus_tgtdeleg 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_tgtdeleg needs a policy

This tool performs a Kerberos credential extraction attack by abusing the delegation mechanism to retrieve a usable TGT without requiring elevated privileges. It is part of a known offensive security/red team toolset (Rubeus) explicitly designed for Kerberos abuse. The action executes an exploitation technique that extracts authentication tickets, which can then be used for lateral movement or privilege escalation.

From the tool's definition 'Extract a usable TGT for the current user without elevation' and 'abuse the delegation mechanism' — this tool exploits a Kerberos GSS-API vulnerability to extract Ticket Granting Tickets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rubeus_tgtdeleg Rate-limited

rubeus_tgtdeleg 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_tgtdeleg": {
      "limits": [
        {
          "counter": "rubeus_tgtdeleg_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_tgtdeleg

What does the rubeus_tgtdeleg tool do? +

Extract a usable TGT for the current user without elevation. Uses Kerberos GSS-API to abuse the delegation mechanism and retrieve the current user. 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_tgtdeleg? +

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

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

Can I rate-limit rubeus_tgtdeleg? +

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

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

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