Edit the API-integration library — workspaces, APIs, request parameters, response configs, input variables, and workspace constants. op is a schema ToolName; args is its payload. Call guide {plugin:"api"} for the rules and arg shapes.
AI agents use 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 | |
args | object | — | |
appExId | string | null | — | |
projectExId | string | — | |
appVersionExId | string | null | — |
Parameters from the server's own tool schema.
This tool creates and modifies API configurations and workspace settings (Write category). It is not destructive since edits are reversible. It is not Execute because it manages configuration data rather than executing arbitrary code or commands.
From the tool's definition Tool description states 'Edit the API-integration library' with capabilities to modify 'workspaces, APIs, request parameters, response configs, input variables, and workspace constants.' The term 'Edit' combined with modification of multiple configuration…
Attacks that exploit this kind of access
Edit the API-integration library — workspaces, APIs, request parameters, response configs, input variables, and workspace constants. op is a schema ToolName; args is its payload. Call guide {plugin:"api"} for the rules and arg shapes. 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.
api accepts 5 parameters: op, args, appExId, 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 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.
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 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 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.
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.
api is one line of Zion's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →