rubeus_ptt · Rubeus MCP Server MCP: Risk & Policy

WHAT IT DOES

What rubeus_ptt does on Rubeus MCP Server

AI agents invoke rubeus_ptt 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_ptt needs a policy

This tool performs a Pass-the-Ticket (PtT) attack, a well-known Kerberos credential abuse technique. It injects a Kerberos ticket into the current logon session to impersonate another user or gain unauthorized access to resources. This is an active exploitation/execution operation — it modifies the authentication state of the current session and enables lateral movement or privilege escalation.

From the tool's definition Pass-the-ticket: Apply a Kerberos ticket to the current logon session. Imports a ticket (from base64 or .kirbi file) into the current session, enabling access to resources as the ticket

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rubeus_ptt Rate-limited

rubeus_ptt 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_ptt": {
      "limits": [
        {
          "counter": "rubeus_ptt_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_ptt

What does the rubeus_ptt tool do? +

Pass-the-ticket: Apply a Kerberos ticket to the current logon session. Imports a ticket (from base64 or .kirbi file) into the current session, enabling access to resources as the ticket. 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_ptt? +

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

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

Can I rate-limit rubeus_ptt? +

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

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

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