Third-party API integrations: workspaces, APIs, parameters, input variables, response configs, and workspace constants. Changes apply immediately; use schema_undo to revert the last change. Ops: - op=ADD → ADD_APIS (req: items) [post-type-system-refactor only] - op=ADD_INPUT_VARIABLES → ADD_API_I...
AI agents use schema_api 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 | |
url | string | — | |
apiId | string | — | |
items | array | — | |
apiIds | array | — | |
method | string | — | |
appExId | string | null | — | |
uniqueIds | array | — | |
useAsData | boolean | — | |
pagination | object | — | |
description | string | — | |
displayName | string | — |
Parameters from the server's own tool schema.
The tool modifies schema configuration for third-party API integrations (adding APIs, parameters, input variables, response configs, workspaces). Changes are applied immediately but are reversible via schema_undo, placing this in the Write category.
From the tool's definition Changes apply immediately; use schema_undo to revert the last change. Ops: ADD_APIS, ADD_API_INPUT_VARIABLES, ADD_API_PARAMETERS, ADD_API_RESPONSE_CONFIGS, ADD_WORKSPACES
Risk signalsAccepts URL/endpoint input (url) · High parameter count (18 properties)
Attacks that exploit this kind of access
Third-party API integrations: workspaces, APIs, parameters, input variables, response configs, and workspace constants. Changes apply immediately; use schema_undo to revert the last change. Ops: - op=ADD → ADD_APIS (req: items) [post-type-system-refactor only] - op=ADD_INPUT_VARIABLES → ADD_API_INPUT_VARIABLES (req: apiId, items) [post-type-system-refactor only] - op=ADD_PARAMETERS → ADD_API_PARAMETERS (req: apiId, items) [post-type-system-refactor only] - op=ADD_RESPONSE_CONFIGS → ADD_API_RESPONSE_CONFIGS (req: apiId, items) [post-type-system-refactor only] - op=ADD_WORKSPACES → ADD_API_WORKSPACES (req: items) [post-type-system-refactor only] - op=ADD_WORKSPACE_CONSTANTS → ADD_API_WORKSPACE_CONSTANTS (req: items, workspaceId) [post-type-system-refactor only] - op=DELETE → DELETE_APIS (req: apiIds) [post-type-system-refactor only] - op=DELETE_INPUT_VARIABLES → DELETE_API_INPUT_VARIABLES (req: apiId, variableNames) [post-type-system-refactor only] - op=DELETE_PARAMETERS → DELETE_API_PARAMETERS (req: apiId, items) [post-type-system-refactor only] - op=DELETE_RESPONSE_CONFIGS → DELETE_API_RESPONSE_CONFIGS (req: apiId, uniqueIds) [post-type-system-refactor only] - op=DELETE_WORKSPACES → DELETE_API_WORKSPACES (req: workspaceIds) [post-type-system-refactor only] - op=DELETE_WORKSPACE_CONSTANTS → DELETE_API_WORKSPACE_CONSTANTS (req: constantNames, workspaceId) [post-type-system-refactor only] - op=LIST → GET_ALL_API_INFOS [post-type-system-refactor only] - op=LIST_WORKSPACES → GET_ALL_API_WORKSPACES [post-type-system-refactor only] - op=GET_DETAIL → GET_API_DETAIL (req: apiId) [post-type-system-refactor only] - op=UPDATE → UPDATE_API (req: apiId) [post-type-system-refactor only] - op=UPDATE_INPUT_VARIABLES → UPDATE_API_INPUT_VARIABLES (req: apiId, items) [post-type-system-refactor only] - op=UPDATE_PARAMETERS → UPDATE_API_PARAMETERS (req: apiId, items) [post-type-system-refactor only] - op=UPDATE_RESPONSE_CONFIGS → UPDATE_API_RESPONSE_CONFIGS (req: apiId, items) [post-type-system-refactor only] - op=UPDATE_WORKSPACE → UPDATE_API_WORKSPACE (req: workspaceId) [post-type-system-refactor only] - op=UPDATE_WORKSPACE_CONSTANTS → UPDATE_API_WORKSPACE_CONSTANTS (req: items, workspaceId) [post-type-system-refactor only]. 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_api accepts 12 parameters: op, url, apiId, items, apiIds, method, appExId, uniqueIds, useAsData, pagination, description, displayName. 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_api: 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_api 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_api 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_api. 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_api 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 →