New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

bazel_visionos_run

Build and launch a Bazel visionOS application via

SERVERXcodeBazelMCP SOURCExcodebazelmcp/xcodebazelmcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-visionos-run.md

What bazel_visionos_run does on XcodeBazelMCP

AI agents invoke bazel_visionos_run 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_visionos_run is rated High

This tool triggers external operations (Bazel build system + application launch) whose side effects depend on the build target and application arguments. It executes code compilation and runs an application in a potentially external environment (visionOS simulator or device), which can modify system state, create processes, and execute arbitrary application logic.

From the tool's definition Tool name 'bazel_visionos_run' and description 'Build and launch a Bazel visionOS application' indicate execution of build operations and application launch on visionOS platform.

Questions about bazel_visionos_run

What does the bazel_visionos_run tool do? +

Build and launch a Bazel visionOS application via. 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.

How do I enforce a policy on bazel_visionos_run? +

Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_visionos_run: 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.

What risk level is bazel_visionos_run? +

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

Can I rate-limit bazel_visionos_run? +

Yes. Add a rate_limit block to the bazel_visionos_run 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 bazel_visionos_run completely? +

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of XcodeBazel's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.