bazel_ios_lldb_sessions

List active LLDB debug sessions.

SERVERXcodeBazelMCP SOURCExcodebazelmcp/xcodebazelmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-ios-lldb-sessions.md

WHAT IT DOES

What bazel_ios_lldb_sessions does on XcodeBazelMCP

AI agents call bazel_ios_lldb_sessions 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.

RISK

Why bazel_ios_lldb_sessions is rated Low

This tool retrieves and displays information about currently active LLDB (Low Level Debugger) debug sessions. It performs a read-only query operation that does not modify, execute, delete, or create any data or processes. The action of listing active sessions is informational only, making it a Read category tool with low severity risk.

From the tool's definition Tool name 'bazel_ios_lldb_sessions' and description 'List active LLDB debug sessions' indicate a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

bazel_ios_lldb_sessions Allowed

bazel_ios_lldb_sessions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect XcodeBazelMCP, apply this rule, and every bazel_ios_lldb_sessions call is checked against it from then on.

FAQ

Questions about bazel_ios_lldb_sessions

What does the bazel_ios_lldb_sessions tool do? +

List active LLDB debug sessions. It is categorised as a Read tool in the XcodeBazelMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bazel_ios_lldb_sessions? +

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

bazel_ios_lldb_sessions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bazel_ios_lldb_sessions? +

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

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

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

KEEP EXPLORING

More on XcodeBazel, and thousands of servers like it.

This server

All 125 XcodeBazel tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →