AI agents invoke fd_exec to trigger actions in Fd. 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 shell commands on bulk file selections, which can perform side effects dependent on the command arguments and target files. While it does not irreversibly delete data by itself (which would be Destructive), it enables arbitrary command execution with potential for unintended consequences.
From the tool's definition Tool description explicitly states 'Execute commands on multiple files' and 'faster & safer than find -exec'. The capability to run arbitrary commands on matched files makes this an Execute tool.
Attacks that exploit this kind of access
⚙️ FAST BULK OPERATIONS: Execute commands on multiple files (faster & safer than find -exec). It is categorised as a Execute tool in the Fd MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Fd MCP server in PolicyLayer and add a rule for fd_exec: 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 Fd. Nothing to install.
fd_exec 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 fd_exec 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 fd_exec. 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.
fd_exec is provided by the Fd MCP server (thhart/fd-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 →