Manage branches of a conditional binding (schemaPath). Build each branch predicate with schema_condition_expr. Changes apply immediately; use schema_undo to revert the last change. Ops: - op=DELETE → DELETE_CONDITIONAL_DATA (req: id, schemaPath) - op=INSERT → INSERT_CONDITIONAL_DATA (req: schemaP...
AI agents use schema_conditional_branch to create or update resources in Zion — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zion environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | — | |
op | string | Yes | |
afterId | string | — | |
appExId | string | null | — | |
schemaPath | array | — | |
projectExId | string | — | |
reorderedIds | array | — | |
conditionData | object | — | |
appVersionExId | string | null | — |
Parameters from the server's own tool schema.
This tool performs multiple operations (insert, update, reorder, delete) on schema conditional branches. While it includes a DELETE op, changes are noted as revertible via schema_undo, suggesting they are not fully irreversible. The most severe non-destructive category is Write, as it creates and modifies schema configuration data.
From the tool's definition Manage branches of a conditional binding... Changes apply immediately; use schema_undo to revert the last change. Ops: DELETE, INSERT, REORDER, UPDATE
Attacks that exploit this kind of access
Manage branches of a conditional binding (schemaPath). Build each branch predicate with schema_condition_expr. Changes apply immediately; use schema_undo to revert the last change. Ops: - op=DELETE → DELETE_CONDITIONAL_DATA (req: id, schemaPath) - op=INSERT → INSERT_CONDITIONAL_DATA (req: schemaPath) - op=REORDER → REORDER_CONDITIONAL_DATA (req: reorderedIds, schemaPath) - op=UPDATE → UPDATE_CONDITIONAL_DATA (req: conditionData, id, schemaPath). It is categorised as a Write tool in the Zion MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
schema_conditional_branch accepts 9 parameters: id, op, afterId, appExId, schemaPath, projectExId, reorderedIds, conditionData, appVersionExId. Required: op. The full parameter table on this page comes from the server's own tool schema.
Register the Zion MCP server in PolicyLayer and add a rule for schema_conditional_branch: 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 Zion. Nothing to install.
schema_conditional_branch 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 schema_conditional_branch 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 schema_conditional_branch. 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.
schema_conditional_branch is provided by the Zion MCP server (zion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →