build_run

What build_run does on Mcp Anything

AI agents invoke build_run to trigger actions in Mcp Anything. 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.

Why build_run is rated High

The tool executes a build system command with side effects that depend on the build configuration and project state. While the description says 'Generate,' build commands in Unity inherently execute compilation and asset processing. This falls under Execute (runs code/commands with external operations) rather than Write, as builds are not simple data modification.

From the tool's definition Tool name is 'build_run' and description states 'Generate the Unity build command' — this generates and triggers a build process, which is code execution with external effects (compilation, asset processing, potential output generation).

The rule that runs build_run safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For build_run, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "build_run": {
      "limits": [
        {
          "counter": "build_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about build_run