Get the call stack (backtrace) for the current or specified thread.
AI agents call bazel_ios_lldb_backtrace to retrieve information from XcodeBazelMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access bazel_ios_lldb_backtrace gives an agent:
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_ios_lldb_backtrace:
{
"version": "1",
"default": "deny",
"tools": {
"bazel_ios_lldb_backtrace": {}
}
}bazel_ios_lldb_backtrace is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the call stack (backtrace) for the current or specified thread. It is categorised as a Read tool in the XcodeBazelMCP MCP Server, which means it retrieves data without modifying state.
Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_ios_lldb_backtrace: 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_backtrace is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the bazel_ios_lldb_backtrace 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_backtrace. 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_backtrace 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.
Start from XcodeBazelMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
117 XcodeBazelMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.