Display a quick summary of all tickets in current/all sessions. Shows ticket information without full extraction - useful for reconnaissance of what tickets are available.
AI agents call rubeus_triage to retrieve information from Rubeus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
While this tool operates in a high-risk domain (Kerberos abuse/credential theft), the rubeus_triage function itself only retrieves and displays ticket metadata. It performs no write, deletion, code execution, or financial operations.
From the tool's definition Tool displays and summarizes ticket information from Kerberos sessions without extraction or modification. Description states 'Display a quick summary' and 'useful for reconnaissance', which are read-only intelligence-gathering operations.
Attacks that exploit this kind of access
Display a quick summary of all tickets in current/all sessions. Shows ticket information without full extraction - useful for reconnaissance of what tickets are available. It is categorised as a Read tool in the Rubeus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rubeus MCP Server MCP server in PolicyLayer and add a rule for rubeus_triage: 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_triage is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the rubeus_triage 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_triage. 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_triage 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 →