AI agents invoke sync_backend to trigger actions in Zion. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
appExId | string | null | — | |
buildTarget | string | — | |
projectExId | string | — | |
appVersionExId | string | null | — | |
validateMultiClient | boolean | — | |
allowValidationErrors | boolean | — |
Parameters from the server's own tool schema.
This tool executes a deployment operation ('deploy/sync') on a backend service, which is fundamentally an Execute action—it triggers external systems and infrastructure changes. While deployment could be considered destructive if it overwrites production systems, the description emphasizes validation and controlled deployment rather than unconditional destruction.
From the tool's definition Tool description states it 'deploy/sync the supportservice backend' and 'blocks on backend validation errors'. The words 'deploy' and 'sync' indicate triggering external operations with effects that depend on the schema argument provided.
Attacks that exploit this kind of access
Save the schema and deploy/sync the supportservice backend. Returns ztype diagnostics and blocks on backend validation errors by default. It is categorised as a Execute tool in the Zion MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
sync_backend accepts 6 parameters: appExId, buildTarget, projectExId, appVersionExId, validateMultiClient, allowValidationErrors. 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 sync_backend: 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.
sync_backend is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sync_backend 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 sync_backend. 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.
sync_backend 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 →