Create a data binding at a binding location (schemaPath). op=OPTION uses a pathInHierarchicalMenu from schema_binding_inspect; op=FORMULA an operator from FORMULA_OPERATORS. operation defaults to REPLACE (CONCAT to append). Changes apply immediately; use schema_undo to revert the last change. Ops...
AI agents use schema_create_binding 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 | |
config | object | — | |
appExId | string | null | — | |
operator | string | — | |
operation | string | — | |
schemaPath | array | — | |
projectExId | string | — | |
constantValue | object | — | |
appVersionExId | string | null | — | |
initialBranchNames | array | — | |
pathInHierarchicalMenu | array | — |
Parameters from the server's own tool schema.
This tool creates or modifies data bindings in a schema, which is a reversible write operation. The explicit mention that changes 'apply immediately' and can be reverted via 'schema_undo' confirms the reversible nature. It does not delete data (Destructive), execute arbitrary code (Execute), or commit financial transactions (Financial).
From the tool's definition Tool description states 'Create a data binding' and 'Changes apply immediately; use schema_undo to revert the last change.' The operations include CREATE_CONDITIONAL_BINDING, CREATE_CONST_BINDING, CREATE_FORMULA_BINDING, CREATE_OPTION_BINDING, and…
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
Create a data binding at a binding location (schemaPath). op=OPTION uses a pathInHierarchicalMenu from schema_binding_inspect; op=FORMULA an operator from FORMULA_OPERATORS. operation defaults to REPLACE (CONCAT to append). Changes apply immediately; use schema_undo to revert the last change. Ops: - op=CONDITIONAL → CREATE_CONDITIONAL_BINDING (req: schemaPath) - op=CONST → CREATE_CONST_BINDING (req: constantValue, schemaPath) - op=FORMULA → CREATE_FORMULA_BINDING (req: schemaPath) - op=OPTION → CREATE_OPTION_BINDING (req: pathInHierarchicalMenu, schemaPath) - op=SET_FORMULA_CONFIG → SET_FORMULA_CONFIG (req: config, 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_create_binding accepts 11 parameters: op, config, appExId, operator, operation, schemaPath, projectExId, constantValue, appVersionExId, initialBranchNames, pathInHierarchicalMenu. 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_create_binding: 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_create_binding 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_create_binding 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_create_binding. 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_create_binding 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 →