bazel_list_workflows
List all available workflow categories, their tools, and whether they are currently enabled. Use this to discover server capabilities and toggle workflows on/off.
This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-list-workflows.md
What bazel_list_workflows does on XcodeBazelMCP
AI agents call bazel_list_workflows 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_list_workflows is rated Low
This tool performs a discovery/introspection function—it retrieves metadata about available capabilities and their enablement status. It has no side effects, does not execute commands, does not modify data, and does not delete or move resources. The mention of 'toggle workflows on/off' in the description refers to what users can do after discovery, but the tool itself only lists/reads the current state.
From the tool's definition Tool name 'list' and description 'List all available workflow categories, their tools, and whether they are currently enabled' indicate a query operation that retrieves and displays information about available workflows without modifying any state.
Attacks that exploit this kind of access
The rule that runs bazel_list_workflows 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_list_workflows, this is the rule to start with:
bazel_list_workflows 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_list_workflows call is checked against it from then on.
Questions about bazel_list_workflows
List all available workflow categories, their tools, and whether they are currently enabled. Use this to discover server capabilities and toggle workflows on/off. 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_list_workflows: 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_list_workflows 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_list_workflows 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_list_workflows. 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_list_workflows 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