list_get

A read tool on the Container- MCP server.

SERVERContainer-MCP SOURCE54rt1n/container-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/54rt1n-container-mcp/list-get.md

WHAT IT DOES

What list_get does on Container-MCP

AI agents call list_get to retrieve information from Container-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_get is rated Low

The name pattern 'list_get' indicates a read operation that retrieves data from a list without modification. However, confidence is reduced because the description is empty, limiting certainty about actual function, potential parameters, and access controls.

From the tool's definition Tool name 'list_get' suggests retrieval of list items; no description provided to confirm scope or behavior.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_get 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_get, this is the rule to start with:

list_get Allowed

list_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_get": {}
  }
}

ALLOW ONLY 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_get call is checked against it from then on.

FAQ

Questions about list_get

What does the list_get tool do? +

list_get is a read tool on the Container MCP server. It is categorised as a Read tool in the Container-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_get? +

Register the Container MCP server in PolicyLayer and add a rule for list_get: 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_get? +

list_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_get? +

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

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

list_get 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →