app_update

Update an installed app

SERVERNasbridge SOURCEmaverick0628/nasbridge

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nasbridge/app-update.md

WHAT IT DOES

What app_update does on Nasbridge

AI agents use app_update to create or update resources in Nasbridge, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nasbridge environment.

RISK

Why app_update is rated Medium

Updating an application is a reversible write operation that modifies existing software state. While the blast radius is notable (application updates can affect system stability, introduce bugs, or cause service interruptions, hence 'high' severity), it falls under the Write category rather than Execute or Destructive.

From the tool's definition Tool name 'app_update' and description 'Update an installed app' indicate a modification operation that changes the state of an installed application.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs app_update safely

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

app_update Rate-limited

app_update stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_update": {
      "limits": [
        {
          "counter": "app_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about app_update

What does the app_update tool do? +

Update an installed app. It is categorised as a Write tool in the Nasbridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on app_update? +

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

What risk level is app_update? +

app_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit app_update? +

Yes. Add a rate_limit block to the app_update 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_update completely? +

Set action: deny in the PolicyLayer policy for app_update. 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_update? +

app_update is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nasbridge, and thousands of servers like it.

This server

All 279 Nasbridge tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →