Run a bash command within the workspace root.
AI agents invoke run_bash to trigger actions in Friday 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.
This tool allows execution of arbitrary bash commands, which can trigger external operations, modify system state, and access/exfiltrate sensitive data depending on command arguments. The blast radius is high if misused by an AI agent—commands could delete files, install malware, exfiltrate secrets, or pivot to other systems.
From the tool's definition Tool explicitly described as 'Run a bash command within the workspace root', enabling arbitrary command execution in a workspace environment.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Run a bash command within the workspace root. It is categorised as a Execute tool in the Friday MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Friday MCP Server MCP server in PolicyLayer and add a rule for run_bash: 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 Friday MCP Server. Nothing to install.
run_bash 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_bash 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_bash. 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_bash is provided by the Friday MCP Server MCP server (jeremylakeyjr/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 →