Edit the boolean condition expression at a binding location (schemaPath). LIST_OPERATORS returns the comparisons available for a term; SET_OPERATOR sets one. Changes apply immediately; use schema_undo to revert the last change. Ops: - op=DELETE_TERM → DELETE_CONDITION_BOOL_EXP (req: schemaPath) -...
AI agents use schema_condition_expr 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 |
|---|---|---|---|
op | string | Yes | |
appExId | string | null | — | |
operator | string | — | |
schemaPath | array | — | |
projectExId | string | — | |
appVersionExId | string | null | — |
Parameters from the server's own tool schema.
This tool modifies schema binding conditions reversibly. While it changes system configuration (the schema structure itself), the operations are reversible via schema_undo, making it Write rather than Destructive.
From the tool's definition Tool description explicitly states 'Changes apply immediately' and includes operations like DELETE_TERM, INSERT_TERM, NEST, TOGGLE_AND_OR, TOGGLE_NOT—all of which modify schema conditions.
Attacks that exploit this kind of access
Edit the boolean condition expression at a binding location (schemaPath). LIST_OPERATORS returns the comparisons available for a term; SET_OPERATOR sets one. Changes apply immediately; use schema_undo to revert the last change. Ops: - op=DELETE_TERM → DELETE_CONDITION_BOOL_EXP (req: schemaPath) - op=LIST_OPERATORS → GET_EXPRESSION_CONDITION_OPERATORS (req: schemaPath) - op=INSERT_TERM → INSERT_CONDITION_BOOL_EXP (req: schemaPath) - op=NEST → NEST_CONDITION_BOOL_EXP (req: schemaPath) - op=TOGGLE_AND_OR → TOGGLE_CONDITION_BOOL_EXP_AND_OR (req: schemaPath) - op=TOGGLE_NOT → TOGGLE_CONDITION_BOOL_EXP_NOT (req: schemaPath) - op=SET_OPERATOR → UPDATE_EXPRESSION_CONDITION_OPERATOR (req: operator, 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_condition_expr accepts 6 parameters: op, appExId, operator, schemaPath, projectExId, 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_condition_expr: 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_condition_expr 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_condition_expr 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_condition_expr. 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_condition_expr 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 →