Run build script with package manager (npm/yarn/pnpm/bun)
AI agents invoke nodejs_build to trigger actions in MCP DevTools 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 fits Execute because it triggers external build operations whose effects depend on the package.json configuration and build script contents. The blast radius is high: a malicious or misconfigured build script could compile malware, exfiltrate secrets, modify source files, or compromise the development environment.
From the tool's definition Tool runs build scripts via package managers (npm/yarn/pnpm/bun). Build scripts execute arbitrary code defined in package.json, which can invoke shell commands, modify files, install dependencies, and trigger side effects beyond the developer's immediate…
Documented attack patterns abuse exactly the kind of access nodejs_build gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP DevTools Server, and nothing reaches the server without passing your rules. This is the rule we recommend for nodejs_build:
{
"version": "1",
"default": "deny",
"tools": {
"nodejs_build": {
"limits": [
{
"counter": "nodejs_build_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}nodejs_build stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run build script with package manager (npm/yarn/pnpm/bun). It is categorised as a Execute tool in the MCP DevTools Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP DevTools Server MCP server in PolicyLayer and add a rule for nodejs_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 MCP DevTools Server. Nothing to install.
nodejs_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 nodejs_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 nodejs_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.
nodejs_build is provided by the MCP DevTools Server MCP server (rshade/mcp-devtools-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP DevTools Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
79 MCP DevTools Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.