bazel_ios_agent_debug_repro
One-shot Cursor debug repro: clear host log → build_and_run with AGENT_DEBUG_* launchEnv → optional log capture.
This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-ios-agent-debug-repro.md
What bazel_ios_agent_debug_repro does on XcodeBazelMCP
AI agents invoke bazel_ios_agent_debug_repro 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_ios_agent_debug_repro is rated High
This tool executes a multi-step operation: it clears logs (destructive sub-action), builds the app, runs it with special debug environment variables, and captures logs. The dominant action is executing a build-and-run pipeline with debug launch environment injection, which constitutes arbitrary code execution. The destructive sub-step (log clear) is subordinate.
From the tool's definition 'One-shot Cursor debug repro: clear host log → build_and_run with AGENT_DEBUG_* launchEnv → optional log capture' — triggers a build, run, and log operations in sequence
Attacks that exploit this kind of access
The rule that runs bazel_ios_agent_debug_repro 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_ios_agent_debug_repro, this is the rule to start with:
bazel_ios_agent_debug_repro 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_ios_agent_debug_repro call is checked against it from then on.
Questions about bazel_ios_agent_debug_repro
One-shot Cursor debug repro: clear host log → build_and_run with AGENT_DEBUG_* launchEnv → optional log capture. 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_ios_agent_debug_repro: 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_ios_agent_debug_repro 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_ios_agent_debug_repro 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_ios_agent_debug_repro. 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_ios_agent_debug_repro 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