list_modify
A write tool on the Container- MCP server.
This record as markdown: /tools/54rt1n-container-mcp/list-modify.md
What list_modify does on Container-MCP
AI agents use list_modify 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.
Why list_modify is rated Medium
The name 'list_modify' implies a write/update operation on some list or collection. With no description available, confidence is low. Given the server context (MCP with file, kb, and container tools), this likely modifies a list resource reversibly. Most severe applicable category without destructive/execute evidence is Write. Severity is medium due to uncertainty about blast radius.
From the tool's definition Tool name 'list_modify' suggests modification of a list structure; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs list_modify 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_modify, this is the rule to start with:
list_modify 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Container-MCP, apply this rule, and every list_modify call is checked against it from then on.
Questions about list_modify
list_modify 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.
Register the Container MCP server in PolicyLayer and add a rule for list_modify: 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.
list_modify is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the list_modify 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 list_modify. 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.
list_modify 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.
More on Container, and thousands of servers like it.
This server
Across the catalogue