list_search
A read tool on the Container- MCP server.
This record as markdown: /tools/54rt1n-container-mcp/list-search.md
What list_search does on Container-MCP
AI agents call list_search 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.
Why list_search is rated Low
The tool name implies searching through or retrieving data from a list structure. Without a description, confidence is moderate, but the naming pattern and presence of other Read-category tools (fs_list, kb_read) on the same server support classification as a retrieval operation with no side effects. No evidence of deletion, modification, or execution.
From the tool's definition Tool name 'list_search' suggests querying or retrieving list items; no description provided to confirm, but naming convention and sibling context (fs_list, kb_read as read operations) indicate search/query functionality without mutation.
Attacks that exploit this kind of access
The rule that runs list_search 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_search, this is the rule to start with:
list_search is read-only, so it stays allowed. 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_search call is checked against it from then on.
Questions about list_search
list_search 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.
Register the Container MCP server in PolicyLayer and add a rule for list_search: 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_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_search 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_search. 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_search 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