bazel_toggle_workflow
Enable or disable a workflow category at runtime. When workflows are filtered, only tools from enabled workflows appear in tools/list. Pass
This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-toggle-workflow.md
What bazel_toggle_workflow does on XcodeBazelMCP
AI agents use bazel_toggle_workflow to create or update resources in XcodeBazelMCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your XcodeBazelMCP environment.
Why bazel_toggle_workflow is rated Medium
This tool modifies the runtime configuration of the MCP server by toggling workflow categories on or off, which affects which tools are visible/available. This is a reversible configuration change (Write), not destructive or financial. Misuse could hide or expose tools from an AI agent, potentially limiting functionality or accidentally enabling dangerous toolsets, warranting medium severity.
From the tool's definition Enable or disable a workflow category at runtime. When workflows are filtered, only tools from enabled workflows appear in tools/list.
Attacks that exploit this kind of access
The rule that runs bazel_toggle_workflow 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_toggle_workflow, this is the rule to start with:
bazel_toggle_workflow stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_toggle_workflow call is checked against it from then on.
Questions about bazel_toggle_workflow
Enable or disable a workflow category at runtime. When workflows are filtered, only tools from enabled workflows appear in tools/list. Pass. It is categorised as a Write tool in the XcodeBazelMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_toggle_workflow: 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_toggle_workflow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bazel_toggle_workflow 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_toggle_workflow. 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_toggle_workflow 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