bazel
Bazel build system operations: build, test, query, info, run, clean, fetch.
This record as markdown: /tools/io-github-dave-london-docker/bazel.md
What bazel does on Docker
AI agents invoke bazel to trigger actions in Docker. 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 bazel is rated High
The 'build', 'test', 'run', and 'clean' operations are Execute-category actions that trigger the Bazel build system to compile code, execute tests, run binaries, and clean build artifacts. While 'query', 'info', and 'fetch' are less severe, the presence of 'run' (executes arbitrary code) and 'build' (compiles and potentially executes build rules) makes this an Execute risk.
From the tool's definition Bazel build system operations including: build, test, run, clean, fetch. These are execution operations that trigger external processes and can compile code, run tests, execute binaries, and modify local build artifacts.
Attacks that exploit this kind of access
The rule that runs bazel safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docker, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bazel, this is the rule to start with:
bazel 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Docker, apply this rule, and every bazel call is checked against it from then on.
Questions about bazel
Bazel build system operations: build, test, query, info, run, clean, fetch. It is categorised as a Execute tool in the Docker MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Docker MCP server in PolicyLayer and add a rule for bazel: 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 Docker. Nothing to install.
bazel 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 bazel 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 bazel. 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.
bazel is provided by the Docker MCP server (@paretools/docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docker, and thousands of servers like it.
Across the catalogue