Request filters (conditional filters / where-conditions / sort) addressed by schemaPath. Start from op=CONTEXT for selectable columns and sub-paths — never hand-build paths. Condition values are DataBindings (fill with schema_create_binding). Changes apply immediately; use schema_undo to revert t...
AI agents use schema_request_filter 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 | |
name | string | — | |
sort | string | — | |
field | array | — | |
index | number | — | |
value | object | — | |
afterId | string | — | |
appExId | string | null | — | |
operator | string | — | |
schemaPath | array | — | |
projectExId | string | — |
Parameters from the server's own tool schema.
The tool modifies project schema configuration by adding or deleting filters, conditions, and sort configurations. Changes are applied immediately but are reversible via schema_undo, placing it in the Write category. The DELETE_FILTER operation could edge toward Destructive, but since undo is available, Write is the most appropriate category.
From the tool's definition Changes apply immediately; use schema_undo to revert the last change. Ops include ADD_FILTER, ADD_CONDITION, ADD_SORT, DELETE_FILTER
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
Request filters (conditional filters / where-conditions / sort) addressed by schemaPath. Start from op=CONTEXT for selectable columns and sub-paths — never hand-build paths. Condition values are DataBindings (fill with schema_create_binding). Changes apply immediately; use schema_undo to revert the last change. Ops: - op=ADD_FILTER → ADD_REQUEST_CONDITIONAL_FILTER (req: schemaPath) - op=ADD_CONDITION → ADD_REQUEST_FILTER_CONDITION (req: columnPathComponents, schemaPath) - op=ADD_SORT → ADD_REQUEST_SORT_CONFIG (req: field, schemaPath) - op=DELETE_FILTER → DELETE_REQUEST_CONDITIONAL_FILTER (req: id, schemaPath) - op=DELETE_CONDITION → DELETE_REQUEST_FILTER_CONDITION (req: schemaPath) - op=DELETE_SORT → DELETE_REQUEST_SORT_CONFIG (req: index, schemaPath) - op=CONTEXT → GET_REQUEST_FILTER_CONTEXT (req: schemaPath) - op=NEST_CONDITION → NEST_REQUEST_FILTER_CONDITION (req: schemaPath) - op=REORDER_FILTERS → REORDER_REQUEST_CONDITIONAL_FILTERS (req: reorderedIds, schemaPath) - op=REORDER_SORT → REORDER_REQUEST_SORT_CONFIGS (req: reorderedIndexes, schemaPath) - op=TOGGLE_CONDITION_AND_OR → TOGGLE_REQUEST_FILTER_CONDITION_AND_OR (req: schemaPath) - op=TOGGLE_CONDITION_NOT → TOGGLE_REQUEST_FILTER_CONDITION_NOT (req: schemaPath) - op=UPDATE_FILTER → UPDATE_REQUEST_CONDITIONAL_FILTER (req: id, name, schemaPath) - op=SET_CONDITION_OPERATOR → UPDATE_REQUEST_FILTER_CONDITION_OPERATOR (req: operator, schemaPath) - op=UPDATE_SORT → UPDATE_REQUEST_SORT_CONFIG (req: index, 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_request_filter accepts 12 parameters: id, op, name, sort, field, index, value, afterId, appExId, operator, schemaPath, projectExId. 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_request_filter: 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_request_filter 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_request_filter 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_request_filter. 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_request_filter 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 →