Set the Bazel iOS workspace and optional Bazel binary path used by later tools.
AI agents use bazel_ios_set_workspace 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.
This tool modifies workspace configuration settings (the workspace path and optionally the Bazel binary path), which are stored state that influences later tool behavior. While not destructive or financially impactful, it is a Write operation because it changes configuration that persists across tool invocations.
From the tool's definition Tool description states it 'Set the Bazel iOS workspace and optional Bazel binary path used by later tools' — the verb 'Set' indicates modification of configuration state that affects subsequent operations.
Documented attack patterns abuse exactly the kind of access bazel_ios_set_workspace 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_set_workspace:
{
"version": "1",
"default": "deny",
"tools": {
"bazel_ios_set_workspace": {
"limits": [
{
"counter": "bazel_ios_set_workspace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}bazel_ios_set_workspace 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.
Free to start. No card required.
Set the Bazel iOS workspace and optional Bazel binary path used by later tools. 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_ios_set_workspace: 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_set_workspace 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_ios_set_workspace 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_set_workspace. 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_set_workspace 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.