update_workflow_start_conditions

WHAT IT DOES

What update_workflow_start_conditions does on Xcode Cloud

AI agents use update_workflow_start_conditions to create or update resources in Xcode Cloud — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xcode Cloud environment.

WHY IT NEEDS A POLICY

Why update_workflow_start_conditions needs a policy

This tool modifies existing workflow configuration by updating start conditions—a reversible change to CI/CD automation parameters. It is Write rather than Execute because it reconfigures workflow triggers rather than directly executing builds.

From the tool's definition Tool name 'update_workflow_start_conditions' with description 'Explicitly update workflow start conditions. Pass null to remove a condition.' indicates modification of workflow configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_workflow_start_conditions Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Xcode Cloud, so you can run agents against it safely.

FAQ

Questions about update_workflow_start_conditions

What does the update_workflow_start_conditions tool do? +

Explicitly update workflow start conditions. Pass null to remove a condition. It is categorised as a Write tool in the Xcode Cloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_workflow_start_conditions? +

Register the Xcode Cloud MCP server in PolicyLayer and add a rule for update_workflow_start_conditions: 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 Xcode Cloud. Nothing to install.

What risk level is update_workflow_start_conditions? +

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

Can I rate-limit update_workflow_start_conditions? +

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

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

update_workflow_start_conditions is provided by the Xcode Cloud MCP server (thatfactory/xcode-cloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.