search_users
AI agents call search_users to retrieve information from Docker Explorer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'search_users' strongly suggests a read-only retrieval operation typical of search functionality. While the description is empty (lowering confidence slightly), the verb 'search' implies querying data without modification. In a Docker context, this likely retrieves user information from images, containers, or registries. No evidence of mutation, execution, or financial impact.
From the tool's definition Tool name 'search_users' indicates a query/search operation; no description provided to confirm scope or side effects.
Attacks that exploit this kind of access
search_users. It is categorised as a Read tool in the Docker Explorer MCP Server, which means it retrieves data without modifying state.
Register the Docker Explorer MCP server in PolicyLayer and add a rule for search_users: 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 Docker Explorer. Nothing to install.
search_users 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 search_users 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 search_users. 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.
search_users is provided by the Docker Explorer MCP server (jar285/mcp-docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →