system_instance_upgrade_check
Read system.instance-upgrade.check through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/system-instance-upgrade-check.md
What system_instance_upgrade_check does on Appaloft
AI agents call system_instance_upgrade_check 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 |
|---|---|---|---|
targetVersion | string | — |
Parameters from the server's own tool schema.
Why system_instance_upgrade_check is rated Low
This tool reads upgrade check status without modifying, deleting, or executing code. It is a read-only query operation that retrieves system upgrade information. The low severity reflects minimal blast radius—an agent misusing this would only retrieve unwanted information about pending upgrades, with no destructive or financial consequences.
From the tool's definition Tool description states 'Read system.instance-upgrade.check' and the verb 'Read' explicitly appears in the description. The operation is framed as a check/query operation that retrieves upgrade status information.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs system_instance_upgrade_check 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_check, this is the rule to start with:
system_instance_upgrade_check 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 system_instance_upgrade_check call is checked against it from then on.
Questions about system_instance_upgrade_check
Read system.instance-upgrade.check 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.
system_instance_upgrade_check accepts 1 parameter: targetVersion. 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_check: 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_check 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 system_instance_upgrade_check 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_check. 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_check 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