send_remote_command

Send a command to a remote client

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/send-remote-command.md

What send_remote_command does on Claude C2

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

This tool sends commands to remote clients, enabling arbitrary code/command execution on external machines. The server context ('command and control of remote systems') and sibling tools (amsi_bypass, bypassuac, browser_creds, defender_exclude) strongly indicate this is a C2 (command-and-control) framework. Misuse could result in full remote system compromise across multiple platforms, making this critical severity.

From the tool's definition 'Send a command to a remote client' — directly executes arbitrary commands on remote systems

Questions about send_remote_command

What does the send_remote_command tool do? +

Send a command to a remote 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.

How do I enforce a policy on send_remote_command? +

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

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

Can I rate-limit send_remote_command? +

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

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

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