Run project build command
AI agents invoke run_build to trigger actions in Coding 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.
Build commands are Execute-category because they trigger compilation, script execution, and potentially run arbitrary build steps defined in project configuration files (Makefile, package.json scripts, gradle, etc.). While typically intended for legitimate purposes, a malicious build configuration or AI misuse could execute harmful scripts.
From the tool's definition Tool runs project build command, which executes code/scripts whose effects depend on build configuration and environment. The name 'run_build' and description 'Run project build command' indicate execution of external operations.
Attacks that exploit this kind of access
Run project build command. It is categorised as a Execute tool in the Coding MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Coding 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 Coding 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 Coding MCP Server MCP server (kieutrongthien/coding-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 →