server_shell

Execute any shell command on C2 server (bash, no sandbox, full permissions). Use sudo for privileged ops.

SERVERClaude C2 SOURCE0xyg3n/claude-c2
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xyg3n-claude-c2/server-shell.md

What server_shell does on Claude C2

AI agents invoke server_shell 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 server_shell is rated High

This tool permits unrestricted execution of arbitrary shell commands with full system permissions on a remote C2 server. While not inherently destructive, the combination of 'any shell command', 'no sandbox', and 'full permissions' means an agent could easily invoke destructive commands (rm -rf, dd), financial harm (exfiltrate credentials, payment processing), lateral movement, or privilege escalation.

From the tool's definition "Execute any shell command on C2 server (bash, no sandbox, full permissions)" - explicit statement that the tool runs arbitrary shell commands without sandboxing restrictions.

Risk signalsAdmin/system-level operation

Questions about server_shell

What does the server_shell tool do? +

Execute any shell command on C2 server (bash, no sandbox, full permissions). Use sudo for privileged ops. 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.

How do I enforce a policy on server_shell? +

Register the Claude C2 MCP server in PolicyLayer and add a rule for server_shell: 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.

What risk level is server_shell? +

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

Can I rate-limit server_shell? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Claude C2's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.