Request Service Tickets (TGS) for specified Service Principal Names (SPNs). Requires a valid TGT (provided as ticket parameter or from current session). Can request tickets for multiple SPNs in one operation. Use cases: - Access specific services after obtaining TGT - Kerberoasting alternative (r...
AI agents invoke rubeus_asktgs 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.
This tool actively performs Kerberos ticket-granting service requests against Active Directory infrastructure, enabling credential harvesting (Kerberoasting), privilege escalation via S4U2Self/S4U2Proxy delegation abuse, and lateral movement. It triggers external Kerberos operations whose effects depend on arguments. The server is explicitly designed for 'Kerberos abuse operations,' confirming offensive security use.
From the tool's definition Request Service Tickets (TGS) for specified Service Principal Names (SPNs)... Kerberoasting alternative (request specific SPN tickets)... S4U2Self/S4U2Proxy prerequisite
Attacks that exploit this kind of access
Request Service Tickets (TGS) for specified Service Principal Names (SPNs). Requires a valid TGT (provided as ticket parameter or from current session). Can request tickets for multiple SPNs in one operation. Use cases: - Access specific services after obtaining TGT - Kerberoasting alternative (request specific SPN tickets) - S4U2Self/S4U2Proxy prerequisite. 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.
Register the Rubeus MCP Server MCP server in PolicyLayer and add a rule for rubeus_asktgs: 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.
rubeus_asktgs is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rubeus_asktgs 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.
Set action: deny in the PolicyLayer policy for rubeus_asktgs. 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.
rubeus_asktgs 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →