app_upgrade

Upgrade an app to a newer version.

SERVERTruenas SOURCEspranab/truenas-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/spranab-truenas-mcp/app-upgrade.md

WHAT IT DOES

What app_upgrade does on Truenas

AI agents invoke app_upgrade to trigger actions in Truenas. 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.

RISK

Why app_upgrade is rated High

Upgrading an application triggers an external operation that modifies the running state of the app (replacing binaries, configs, potentially restarting services). It is not a simple write/read, but an active execution that changes system state. Misuse could cause service disruption or incompatibility, hence high severity.

From the tool's definition Upgrade an app to a newer version

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs app_upgrade safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Truenas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For app_upgrade, this is the rule to start with:

app_upgrade Rate-limited

app_upgrade 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "app_upgrade": {
      "limits": [
        {
          "counter": "app_upgrade_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Truenas, apply this rule, and every app_upgrade call is checked against it from then on.

FAQ

Questions about app_upgrade

What does the app_upgrade tool do? +

Upgrade an app to a newer version. It is categorised as a Execute tool in the Truenas MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on app_upgrade? +

Register the Truenas MCP server in PolicyLayer and add a rule for app_upgrade: 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 Truenas. Nothing to install.

What risk level is app_upgrade? +

app_upgrade is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit app_upgrade? +

Yes. Add a rate_limit block to the app_upgrade 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.

How do I block app_upgrade completely? +

Set action: deny in the PolicyLayer policy for app_upgrade. 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.

What MCP server provides app_upgrade? +

app_upgrade is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Truenas, and thousands of servers like it.

This server

All 279 Truenas tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →