build_ota · XR875 Build MCP: Risk & Policy

WHAT IT DOES

What build_ota does on XR875 Build MCP

AI agents invoke build_ota to trigger actions in XR875 Build MCP. 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 IT NEEDS A POLICY

Why build_ota needs a policy

This tool executes a sequence of shell commands that trigger external build processes. While the immediate output is firmware artifacts (reversible via rebuilding), the tool itself invokes arbitrary external operations whose full effects depend on the build environment state and arguments.

From the tool's definition Tool description explicitly shows shell command execution: 'lunch_rtos 35 && ota_mrtos clean && ota_mrtos'. These are chained commands that run external build operations with side effects (cleaning and building OTA artifacts).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

build_ota Rate-limited

build_ota 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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches XR875 Build MCP, so you can run agents against it safely.

FAQ

Questions about build_ota

What does the build_ota tool do? +

Build the M33 OTA (lunch_rtos 35 && ota_mrtos clean && ota_mrtos). It is categorised as a Execute tool in the XR875 Build MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on build_ota? +

Register the XR875 Build MCP server in PolicyLayer and add a rule for build_ota: 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 XR875 Build MCP. Nothing to install.

What risk level is build_ota? +

build_ota is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit build_ota? +

Yes. Add a rate_limit block to the build_ota 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.

How do I block build_ota completely? +

Set action: deny in the PolicyLayer policy for build_ota. 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.

What MCP server provides build_ota? +

build_ota is provided by the XR875 Build MCP server (unicorn2439614256/xr875-build-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.