High Risk →

app_upgrade

Upgrade an app to a newer version.

How to control app_upgrade ↓

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.

High Risk

Why app_upgrade needs a policy

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

Documented attack patterns abuse exactly the kind of access app_upgrade gives an agent:

How to control app_upgrade

PolicyLayer is an MCP gateway — it sits between your AI agents and Truenas, and nothing reaches the server without passing your rules. This is the rule we recommend for app_upgrade:

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

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.

  1. Create a free account and register Truenas — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

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.

Enforce policy on every Truenas tool call.

Start from Truenas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

279 Truenas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.