Read and parse an agent debug NDJSON log. Returns structured entries grouped by hypothesisId/runId with status hints.
AI agents call bazel_ios_agent_debug_log_read 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.
This tool retrieves and parses existing debug log data without creating, modifying, deleting, or executing anything. It has no side effects and presents minimal security risk—reading logs is a standard diagnostic activity. The blast radius of misuse is low, as the agent can only observe information already present in debug logs.
From the tool's definition Tool description explicitly states "Read and parse an agent debug NDJSON log" and returns structured entries. The verb "Read" and the absence of any modification, deletion, or execution capabilities indicate this is a pure data retrieval operation.
Documented attack patterns abuse exactly the kind of access bazel_ios_agent_debug_log_read 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_agent_debug_log_read:
{
"version": "1",
"default": "deny",
"tools": {
"bazel_ios_agent_debug_log_read": {}
}
}bazel_ios_agent_debug_log_read 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.
Read and parse an agent debug NDJSON log. Returns structured entries grouped by hypothesisId/runId with status hints. 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_read: 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_read 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_read 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_read. 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_read 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.