New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

bazel_daemon_status

Check whether the per-workspace daemon is running and list active background operations.

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-daemon-status.md

What bazel_daemon_status does on XcodeBazelMCP

AI agents call bazel_daemon_status 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_daemon_status is rated Low

This is a status/query tool that retrieves information about daemon state and background operations. It has no side effects, makes no modifications, and does not execute external commands or trigger operations. It fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch)'. The severity is low because misuse would only return information without causing harm.

From the tool's definition The tool description explicitly states it 'Check[s] whether the per-workspace daemon is running and list[s] active background operations' — both read-only operations that query daemon state without modifying or executing anything.

Questions about bazel_daemon_status

What does the bazel_daemon_status tool do? +

Check whether the per-workspace daemon is running and list active background operations. 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_daemon_status? +

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

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

Can I rate-limit bazel_daemon_status? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of XcodeBazel's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.