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

bazel_ios_lldb_detach

Detach LLDB from a process and end the debug session.

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-ios-lldb-detach.md

What bazel_ios_lldb_detach does on XcodeBazelMCP

AI agents invoke bazel_ios_lldb_detach 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_detach is rated High

This tool executes a debugger operation — detaching LLDB from a running process and terminating the debug session. It triggers an external operation (interacting with the LLDB debugger and the process being debugged) whose effects depend on the current debug context. It does not merely read data, nor does it irreversibly delete or modify persisted data, making Execute the most appropriate category.

From the tool's definition Detach LLDB from a process and end the debug session

Questions about bazel_ios_lldb_detach

What does the bazel_ios_lldb_detach tool do? +

Detach LLDB from a process and end the debug session. 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_ios_lldb_detach? +

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

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

Can I rate-limit bazel_ios_lldb_detach? +

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

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

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