bazel_macos_app_path

THE RISK

Low Risk

Why bazel_macos_app_path needs a policy

This tool performs a read-only lookup of filesystem paths where compiled macOS applications are located. It retrieves information about build artifacts but does not execute code, modify data, or cause side effects. The operation is equivalent to a file system query or list operation, making it a Read category tool with low severity.

From the tool's definition Tool name and description indicate it 'Locate[s] the .app bundle for a macOS Bazel target in bazel-bin' — a query operation that retrieves path information without modifying or executing anything.

Documented attack patterns abuse exactly the kind of access bazel_macos_app_path gives an agent:

POLICY

How to control bazel_macos_app_path

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_macos_app_path:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bazel_macos_app_path": {}
  }
}

bazel_macos_app_path is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register XcodeBazelMCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More XcodeBazelMCP tools

Destructive bazel_ios_agent_debug_log_clear Delete an agent debug NDJSON log file before a repro run (Cursor debug mode). Safe no-op i Destructive bazel_ios_clean Clean Bazel build outputs. Use expunge to remove the entire output base. Destructive bazel_ios_erase_simulator Erase all content and settings from a simulator, restoring it to factory state. Destructive swift_package_clean Clean build artifacts of a Swift package ( Destructive bazel_ios_device_unpair Unpair a previously paired physical iOS device. Execute bazel_ios_agent_debug_repro One-shot Cursor debug repro: clear host log → build_and_run with AGENT_DEBUG_ launchEnv → Execute bazel_ios_lldb_breakpoint Set a breakpoint by file+line, symbol name, or delete/list breakpoints. Execute bazel_ios_privacy Grant, revoke, or reset privacy permissions for an app on a simulator.

All 117 XcodeBazelMCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about bazel_macos_app_path

What does the bazel_macos_app_path tool do? +

Locate the .app bundle for a macOS Bazel target in bazel-bin. It is categorised as a Read tool in the XcodeBazelMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bazel_macos_app_path? +

Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_macos_app_path: 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_macos_app_path? +

bazel_macos_app_path is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bazel_macos_app_path? +

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

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

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

Enforce policy on every XcodeBazelMCP tool call.

Start from XcodeBazelMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →