Execute a shell script command line against a running agent. This script is executed using the default command line interpreter.
AI agents invoke run_shell_command to trigger actions in Mythic MCP. 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 executes arbitrary shell commands through a C2 agent, which is a core Execute category action. The blast radius is critical because shell commands can have unbounded side effects depending on arguments—file system modification, process termination, credential theft, lateral movement, or complete system compromise.
From the tool's definition Tool description states: 'Execute a shell script command line against a running agent.' The explicit use of 'Execute' and 'shell script command line' indicates arbitrary command execution.
Documented attack patterns abuse exactly the kind of access run_shell_command gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mythic MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for run_shell_command:
{
"version": "1",
"default": "deny",
"tools": {
"run_shell_command": {
"limits": [
{
"counter": "run_shell_command_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_shell_command 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.
Free to start. No card required.
Execute a shell script command line against a running agent. This script is executed using the default command line interpreter. It is categorised as a Execute tool in the Mythic MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mythic MCP server in PolicyLayer and add a rule for run_shell_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 Mythic MCP. Nothing to install.
run_shell_command 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 run_shell_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.
Set action: deny in the PolicyLayer policy for run_shell_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.
run_shell_command is provided by the Mythic MCP server (xpn/mythic_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Mythic MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Mythic MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.