control_plane_portability_import_plan
Read control-plane-portability.import-plan through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/control-plane-portability-import-plan.md
What control_plane_portability_import_plan does on Appaloft
AI agents call control_plane_portability_import_plan to retrieve information from Appaloft without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
mode | string | Yes | |
passphrase | string | Yes | |
encryptedEnvelope | string | Yes |
Parameters from the server's own tool schema.
Why control_plane_portability_import_plan is rated Low
The tool description states it 'reads' an import plan from the control plane portability catalog. Reading/retrieving a plan is a non-destructive, side-effect-free operation. Severity is low as it only retrieves plan data. Confidence is moderate because the description is sparse and 'import-plan' could imply some execution context, but the explicit 'Read' verb takes precedence.
From the tool's definition 'Read control-plane-portability.import-plan' — the description explicitly starts with 'Read'
Attacks that exploit this kind of access
The rule that runs control_plane_portability_import_plan 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_plan, this is the rule to start with:
control_plane_portability_import_plan is read-only, so it stays allowed. 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_plan call is checked against it from then on.
Questions about control_plane_portability_import_plan
Read control-plane-portability.import-plan through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Read tool in the Appaloft MCP Server, which means it retrieves data without modifying state.
control_plane_portability_import_plan accepts 3 parameters: mode, passphrase, encryptedEnvelope. 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_plan: 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_plan is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the control_plane_portability_import_plan 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_plan. 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_plan 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.
This server
Across the catalogue