control_plane_portability_import
Run control-plane-portability.import through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/control-plane-portability-import.md
What control_plane_portability_import does on Appaloft
AI agents invoke control_plane_portability_import to trigger actions in Appaloft. 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 |
|---|---|---|---|
mode | string | Yes | |
passphrase | string | Yes | |
encryptedEnvelope | string | Yes | |
acknowledgeReplace | boolean | — |
Parameters from the server's own tool schema.
Why control_plane_portability_import is rated High
The tool 'runs' an import operation through the control plane, which involves executing an external operation that imports configuration or infrastructure state. Import operations can have significant side effects (overwriting existing configurations, altering deployed resources), making this Execute at minimum.
From the tool's definition 'Run control-plane-portability.import through the Appaloft application operation catalog'
Attacks that exploit this kind of access
The rule that runs control_plane_portability_import safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For control_plane_portability_import, this is the rule to start with:
control_plane_portability_import stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every control_plane_portability_import call is checked against it from then on.
Questions about control_plane_portability_import
Run control-plane-portability.import through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Execute tool in the Appaloft MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
control_plane_portability_import accepts 4 parameters: mode, passphrase, encryptedEnvelope, acknowledgeReplace. Required: mode, passphrase, encryptedEnvelope. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for control_plane_portability_import: 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 Appaloft. Nothing to install.
control_plane_portability_import 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 control_plane_portability_import 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 control_plane_portability_import. 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.
control_plane_portability_import is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
Across the catalogue