rubeus_asktgt · Rubeus MCP Server MCP: Risk & Policy

WHAT IT DOES

What rubeus_asktgt does on Rubeus MCP Server

AI agents invoke rubeus_asktgt 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_asktgt needs a policy

This tool performs Kerberos authentication abuse by requesting TGTs using stolen credentials (passwords, hashes, or certificates) and can inject them into sessions via Pass-the-Ticket (PTT). It is a core offensive security/attack tool enabling lateral movement and privilege escalation in Active Directory environments.

From the tool's definition Request a Ticket Granting Ticket (TGT) using user credentials... Obtain TGT for lateral movement... Support subsequent ticket operations... applied to the current session (PTT)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rubeus_asktgt Rate-limited

rubeus_asktgt 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_asktgt": {
      "limits": [
        {
          "counter": "rubeus_asktgt_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_asktgt

What does the rubeus_asktgt tool do? +

Request a Ticket Granting Ticket (TGT) using user credentials. Supports multiple authentication methods: - Password-based (cleartext or encrypted) - Hash-based (RC4/NTLM, AES128, AES256, DES) - Certificate-based (PKINIT) The TGT can be saved to a file, applied to the current session (PTT), or returned as base64. Example use cases: - Obtain TGT for lateral movement - Test credential validity - Support subsequent ticket operations. 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_asktgt? +

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

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

Can I rate-limit rubeus_asktgt? +

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

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

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