Inspect a data-binding location (schemaPath: DiffPathComponents) — selectable options, expected type, and formula operators/config. Feed a returned path into schema_create_binding. Changes apply immediately; use schema_undo to revert the last change. Ops: - op=BINDING_OPTIONS → GET_DATA_BINDING_O...
AI agents call schema_binding_inspect to retrieve information from Zion without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
op | string | Yes | |
appExId | string | null | — | |
schemaPath | array | — | |
projectExId | string | — | |
appVersionExId | string | null | — |
Parameters from the server's own tool schema.
schema_binding_inspect is a pure read operation that inspects and returns metadata about data-binding locations and formula configurations. Although the description mentions 'Changes apply immediately' in a general context about the schema system, this specific tool only retrieves information via GET operations. The note about schema_undo refers to other operations on the server, not this tool itself.
From the tool's definition The tool performs inspection operations: 'GET_DATA_BINDING_OPTIONS', 'GET_DATA_BINDING_TYPE', 'GET_FORMULA_CONFIG_OPTIONS', and 'GET_FORMULA_OPERATORS'. These are all read-only queries that retrieve information about schema bindings and configuration.
Attacks that exploit this kind of access
Inspect a data-binding location (schemaPath: DiffPathComponents) — selectable options, expected type, and formula operators/config. Feed a returned path into schema_create_binding. Changes apply immediately; use schema_undo to revert the last change. Ops: - op=BINDING_OPTIONS → GET_DATA_BINDING_OPTIONS (req: schemaPath) - op=BINDING_TYPE → GET_DATA_BINDING_TYPE (req: schemaPath) - op=FORMULA_CONFIG_OPTIONS → GET_FORMULA_CONFIG_OPTIONS (req: schemaPath) - op=FORMULA_OPERATORS → GET_FORMULA_OPERATORS (req: schemaPath). It is categorised as a Read tool in the Zion MCP Server, which means it retrieves data without modifying state.
schema_binding_inspect accepts 5 parameters: op, appExId, 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_binding_inspect: 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_binding_inspect is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the schema_binding_inspect 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_binding_inspect. 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_binding_inspect 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 →