bazel_upgrade
Upgrade XcodeBazelMCP to the latest version. Auto-detects install method (npm, Homebrew, source).
This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-upgrade.md
What bazel_upgrade does on XcodeBazelMCP
AI agents invoke bazel_upgrade to trigger actions in XcodeBazelMCP. 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_upgrade is rated High
This tool upgrades the MCP server software itself by running package manager commands (npm, Homebrew, or source builds). It executes external operations that modify the installed software environment. While it could be considered a Write, it actually triggers external execution of package manager commands (npm install, brew upgrade, etc.) and modifies system-level software, making Execute the most accurate category.
From the tool's definition Upgrade XcodeBazelMCP to the latest version. Auto-detects install method (npm, Homebrew, source).
Attacks that exploit this kind of access
The rule that runs bazel_upgrade safely
PolicyLayer is an MCP gateway: it sits between your AI agents and XcodeBazelMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bazel_upgrade, this is the rule to start with:
bazel_upgrade 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 XcodeBazelMCP, apply this rule, and every bazel_upgrade call is checked against it from then on.
Questions about bazel_upgrade
Upgrade XcodeBazelMCP to the latest version. Auto-detects install method (npm, Homebrew, source). It is categorised as a Execute tool in the XcodeBazelMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_upgrade: 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 XcodeBazelMCP. Nothing to install.
bazel_upgrade 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_upgrade 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_upgrade. 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_upgrade is provided by the XcodeBazel MCP server (xcodebazelmcp/xcodebazelmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on XcodeBazel, and thousands of servers like it.
Across the catalogue