Import one or more Third-Party API (TPA) configs from an OpenAPI v3 spec. Provide the spec as a url (fetched from this machine) or paste it as specText (JSON or YAML). Each operation becomes a TPA endpoint with its request parameters and success/fail response shape. Capped at 25 endpoints per cal...
AI agents use import_tpa_from_openapi 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 |
|---|---|---|---|
url | string | — | |
appExId | string | null | — | |
specText | string | — | |
pathsFilter | array | — | |
projectExId | string | — | |
appVersionExId | string | null | — |
Parameters from the server's own tool schema.
This tool creates and modifies data structures (TPA configs and endpoints) within projects, which is a Write-category action. Severity is medium because: (1) the data created can be deleted via sibling tool delete_project or other reversal mechanisms, (2) scope is limited to API endpoint configuration rather than core data, and (3) the rollback behavior on failure mitigates some risk.
From the tool's definition Tool description states it performs import operations that create TPA configs and endpoints, modifying project data: 'Import one or more Third-Party API (TPA) configs', 'Each operation becomes a TPA endpoint', 'Duplicates are created (not merged) with a…
Risk signalsAccepts URL/endpoint input (url) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Import one or more Third-Party API (TPA) configs from an OpenAPI v3 spec. Provide the spec as a url (fetched from this machine) or paste it as specText (JSON or YAML). Each operation becomes a TPA endpoint with its request parameters and success/fail response shape. Capped at 25 endpoints per call — use pathsFilter to scope larger specs. On any failure the whole import is rolled back. Duplicates are created (not merged) with a numbered name suffix. Works on every project generation. 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.
import_tpa_from_openapi accepts 6 parameters: url, appExId, specText, pathsFilter, projectExId, appVersionExId. 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 import_tpa_from_openapi: 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.
import_tpa_from_openapi 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 import_tpa_from_openapi 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 import_tpa_from_openapi. 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.
import_tpa_from_openapi 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 →