bazel_ios_lldb_attach
Attach LLDB debugger to a running process by PID or process name. Returns a session ID for subsequent debug commands.
This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-ios-lldb-attach.md
What bazel_ios_lldb_attach does on XcodeBazelMCP
AI agents invoke bazel_ios_lldb_attach 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_lldb_attach is rated High
Attaching a debugger (LLDB) to a running process is an Execute-category action — it triggers an external debugging operation that can inspect and manipulate the target process's memory, state, and execution flow. Misuse could allow arbitrary code execution, memory reads/writes, or process manipulation. The return of a session ID for subsequent debug commands further amplifies the blast radius.
From the tool's definition Attach LLDB debugger to a running process by PID or process name
Attacks that exploit this kind of access
The rule that runs bazel_ios_lldb_attach 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_lldb_attach, this is the rule to start with:
bazel_ios_lldb_attach 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_lldb_attach call is checked against it from then on.
Questions about bazel_ios_lldb_attach
Attach LLDB debugger to a running process by PID or process name. Returns a session ID for subsequent debug commands. 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_lldb_attach: 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_lldb_attach 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_lldb_attach 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_lldb_attach. 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_lldb_attach 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