Run the build script in the workspace
AI agents invoke run_build to trigger actions in Node Dev 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 triggers execution of a build script, whose effects depend entirely on what the build script contains. Build scripts commonly invoke compilers, package managers, external services, and arbitrary shell commands. While not inherently destructive or financial, execution is uncontrolled and could produce wide-ranging effects (file modifications, network calls, process spawning).
From the tool's definition Tool name is 'run_build' and description states it 'Run the build script in the workspace'. The server description explicitly mentions 'execute build or dependency scripts'.
Attacks that exploit this kind of access
Run the build script in the workspace. It is categorised as a Execute tool in the Node Dev MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Node Dev MCP Server MCP server in PolicyLayer and add a rule for run_build: 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 Node Dev MCP Server. Nothing to install.
run_build 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_build 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_build. 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_build is provided by the Node Dev MCP Server MCP server (liamcarver/node-dev-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 →