bazel_ios_agent_debug_log_pull
Pull agent-debug.ndjson from a simulator app data container (Documents/agent-debug.ndjson) via simctl get_app_container.
This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-ios-agent-debug-log-pull.md
What bazel_ios_agent_debug_log_pull does on XcodeBazelMCP
AI agents call bazel_ios_agent_debug_log_pull 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_agent_debug_log_pull is rated Low
This tool retrieves debug logs from a simulator's file system. It is a read-only operation that queries existing data (the agent debug log file) without creating, modifying, deleting, or executing code. The action is a passive data retrieval from a development simulator environment, posing minimal security risk in isolation.
From the tool's definition Tool 'pull[s] agent-debug.ndjson from a simulator app data container' via 'simctl get_app_container' — a retrieval operation that reads log data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs bazel_ios_agent_debug_log_pull 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_agent_debug_log_pull, this is the rule to start with:
bazel_ios_agent_debug_log_pull is read-only, so it stays allowed. 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_agent_debug_log_pull call is checked against it from then on.
Questions about bazel_ios_agent_debug_log_pull
Pull agent-debug.ndjson from a simulator app data container (Documents/agent-debug.ndjson) via simctl get_app_container. 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_agent_debug_log_pull: 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_agent_debug_log_pull 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_agent_debug_log_pull 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_agent_debug_log_pull. 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_agent_debug_log_pull 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.
This server
Across the catalogue