Create a new process with network credentials (logon type 9). Creates a process that uses different credentials for network authentication. Useful for applying tickets to a separate process. The process can be hidden or visible.
AI agents invoke rubeus_createnetonly 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 spawns a new process with injected network credentials (logon type 9 / NewCredentials), a classic lateral movement technique used in Kerberos abuse. It executes an external process with potentially stolen or forged credentials.
From the tool's definition 'Create a new process with network credentials (logon type 9)' and 'Creates a process that uses different credentials for network authentication'
Attacks that exploit this kind of access
Create a new process with network credentials (logon type 9). Creates a process that uses different credentials for network authentication. Useful for applying tickets to a separate process. The process can be hidden or visible. 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_createnetonly: 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_createnetonly 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_createnetonly 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_createnetonly. 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_createnetonly 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 →