Run Bash commands on a specific site.
AI agents invoke pressable_run_bash_commands to trigger actions in Pressable MCP 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 arbitrary bash commands on a production WordPress site represents critical risk. An AI agent with access to this tool could execute malicious commands, exfiltrate data, install backdoors, modify site files, compromise server security, or pivot to other infrastructure.
From the tool's definition Tool name explicitly states 'run_bash_commands' and description confirms it executes 'Bash commands on a specific site'. This is arbitrary code execution on a server.
Attacks that exploit this kind of access
Run Bash commands on a specific site. It is categorised as a Execute tool in the Pressable MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pressable MCP Server MCP server in PolicyLayer and add a rule for pressable_run_bash_commands: 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 Pressable MCP Server. Nothing to install.
pressable_run_bash_commands 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 pressable_run_bash_commands 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 pressable_run_bash_commands. 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.
pressable_run_bash_commands is provided by the Pressable MCP Server MCP server (pcwprops/pressable-mcp-server). 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 →