system_instance_upgrade_apply
Run system.instance-upgrade.apply through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/system-instance-upgrade-apply.md
What system_instance_upgrade_apply does on Appaloft
AI agents invoke system_instance_upgrade_apply 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 |
|---|---|---|---|
confirm | boolean | Yes | |
targetVersion | string | — |
Parameters from the server's own tool schema.
Why system_instance_upgrade_apply is rated High
The tool executes a system-level upgrade operation on an instance. 'Run' and 'apply' indicate execution of an operation with real side effects (modifying system state by upgrading an instance). While it could be partially destructive if the upgrade is irreversible, upgrades are typically executable operations rather than pure destruction.
From the tool's definition 'Run system.instance-upgrade.apply through the Appaloft application operation catalog'
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs system_instance_upgrade_apply 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 system_instance_upgrade_apply, this is the rule to start with:
system_instance_upgrade_apply 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 system_instance_upgrade_apply call is checked against it from then on.
Questions about system_instance_upgrade_apply
Run system.instance-upgrade.apply 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.
system_instance_upgrade_apply accepts 2 parameters: confirm, targetVersion. Required: confirm. 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 system_instance_upgrade_apply: 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.
system_instance_upgrade_apply 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 system_instance_upgrade_apply 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 system_instance_upgrade_apply. 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.
system_instance_upgrade_apply 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