Run a shell command via Aider
AI agents invoke aider_run_command to trigger actions in Aider MCP WebSocket 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.
Running shell commands is a quintessential Execute category action, as the effects depend entirely on the command arguments provided by the AI agent. With shell access, an agent could read sensitive files, modify system state, exfiltrate data, or cause denial of service.
From the tool's definition Tool name 'aider_run_command' and description 'Run a shell command via Aider' explicitly indicate execution of arbitrary shell commands.
Attacks that exploit this kind of access
Run a shell command via Aider. It is categorised as a Execute tool in the Aider MCP WebSocket Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aider MCP WebSocket Server MCP server in PolicyLayer and add a rule for aider_run_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 Aider MCP WebSocket Server. Nothing to install.
aider_run_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 aider_run_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 aider_run_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.
aider_run_command is provided by the Aider MCP WebSocket Server MCP server (larock22/aider-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 →