Check if a newer version of XcodeBazelMCP is available.
AI agents call bazel_check_update to retrieve information from XcodeBazelMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only check against a remote service (or local cache) to determine if an update is available. It retrieves data about available versions but takes no action to install, modify, or execute anything. There are no side effects beyond information retrieval. Severity is low because misuse poses no meaningful risk—an AI agent checking for updates repeatedly causes no harm.
From the tool's definition Tool name 'bazel_check_update' and description 'Check if a newer version of XcodeBazelMCP is available' indicate a query operation that retrieves version information without modifying, executing, or destructively affecting any system.
Documented attack patterns abuse exactly the kind of access bazel_check_update gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and XcodeBazelMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for bazel_check_update:
{
"version": "1",
"default": "deny",
"tools": {
"bazel_check_update": {}
}
}bazel_check_update is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if a newer version of XcodeBazelMCP is available. It is categorised as a Read tool in the XcodeBazelMCP MCP Server, which means it retrieves data without modifying state.
Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_check_update: 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_check_update is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the bazel_check_update 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_check_update. 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_check_update 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.
Start from XcodeBazelMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
117 XcodeBazelMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.