This record as markdown: /tools/0xyg3n-claude-c2/runas.md
What runas does on Claude C2
AI agents invoke runas to trigger actions in Claude C2. 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 runas is rated High
This tool executes code/commands under a different user context, potentially with elevated privileges. The ability to run arbitrary commands as a different user (especially with escalation potential given the sibling tools like 'bypassuac' and 'defender_exclude' on the same server) represents a critical blast radius if misused by an AI agent—it could lead to unauthorized privilege escalation, lateral movement, or…
From the tool's definition "Run as different user" - executes commands with elevated or alternate user privileges, which are external operations whose effects depend on arguments (user identity, command to execute).
Attacks that exploit this kind of access
The rule that runs runas safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude C2, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For runas, this is the rule to start with:
runas 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude C2, apply this rule, and every runas call is checked against it from then on.
Questions about runas
Run as different user. Auto-selects client. It is categorised as a Execute tool in the Claude C2 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude C2 MCP server in PolicyLayer and add a rule for runas: 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 Claude C2. Nothing to install.
runas 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 runas 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 runas. 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.
runas is provided by the Claude C2 MCP server (0xyg3n/claude-c2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude C2, and thousands of servers like it.
Across the catalogue