list_update

A write tool on the Container- MCP server.

SERVERContainer-MCP SOURCE54rt1n/container-mcp

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/54rt1n-container-mcp/list-update.md

WHAT IT DOES

What list_update does on Container-MCP

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

RISK

Why list_update is rated Medium

The name implies a Write operation (updating a list), but the empty description provides no confirmation. Given the server context (MCP with file, KB, and execution capabilities), this likely modifies some list resource. Confidence is low due to the absent description. Severity is medium as list modifications are typically reversible writes.

From the tool's definition Tool name 'list_update' suggests modifying a list or collection; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_update safely

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

list_update Rate-limited

list_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": {
    "list_update": {
      "limits": [
        {
          "counter": "list_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 Container-MCP, apply this rule, and every list_update call is checked against it from then on.

FAQ

Questions about list_update

What does the list_update tool do? +

list_update is a write tool on the Container MCP server. It is categorised as a Write tool in the Container-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on list_update? +

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

What risk level is list_update? +

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

Can I rate-limit list_update? +

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

Set action: deny in the PolicyLayer policy for list_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 list_update? +

list_update is provided by the Container MCP server (54rt1n/container-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Container, and thousands of servers like it.

This server

All 27 Container tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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