bazel_toggle_workflow

THE RISK

Medium Risk

Why bazel_toggle_workflow needs a policy

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.

Documented attack patterns abuse exactly the kind of access bazel_toggle_workflow gives an agent:

POLICY

How to control bazel_toggle_workflow

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_toggle_workflow:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bazel_toggle_workflow": {
      "limits": [
        {
          "counter": "bazel_toggle_workflow_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

Create a free account and register XcodeBazelMCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More XcodeBazelMCP tools

Destructive bazel_ios_agent_debug_log_clear Delete an agent debug NDJSON log file before a repro run (Cursor debug mode). Safe no-op i Destructive bazel_ios_clean Clean Bazel build outputs. Use expunge to remove the entire output base. Destructive bazel_ios_erase_simulator Erase all content and settings from a simulator, restoring it to factory state. Destructive swift_package_clean Clean build artifacts of a Swift package ( Destructive bazel_ios_device_unpair Unpair a previously paired physical iOS device. Execute bazel_ios_agent_debug_repro One-shot Cursor debug repro: clear host log → build_and_run with AGENT_DEBUG_ launchEnv → Execute bazel_ios_lldb_breakpoint Set a breakpoint by file+line, symbol name, or delete/list breakpoints. Execute bazel_ios_privacy Grant, revoke, or reset privacy permissions for an app on a simulator.

All 117 XcodeBazelMCP tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about bazel_toggle_workflow

What does the bazel_toggle_workflow tool do? +

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.

How do I enforce a policy on bazel_toggle_workflow? +

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.

What risk level is bazel_toggle_workflow? +

bazel_toggle_workflow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit bazel_toggle_workflow? +

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.

How do I block bazel_toggle_workflow completely? +

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.

What MCP server provides bazel_toggle_workflow? +

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.

Enforce policy on every XcodeBazelMCP tool call.

Start from XcodeBazelMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →