bazel_ios_lldb_backtrace

What bazel_ios_lldb_backtrace does on XcodeBazelMCP

AI agents call bazel_ios_lldb_backtrace to retrieve information from XcodeBazelMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why bazel_ios_lldb_backtrace is rated Low

The tool retrieves debugging information (call stack traces) from a running debugger session. This is a non-destructive, informational operation typical of debugging workflows. While it provides internal program state visibility, it does not execute code, modify data, delete resources, or trigger side effects. It falls squarely in the Read category as it 'queries' runtime state for diagnostic purposes.

From the tool's definition Tool name and description indicate retrieval of call stack/backtrace information: 'Get the call stack (backtrace) for the current or specified thread.' This is a read-only debugging operation that queries state without modifying or executing code.

The rule that runs bazel_ios_lldb_backtrace 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_backtrace, this is the rule to start with:

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

Questions about bazel_ios_lldb_backtrace