List all docks
AI agents call vtex_list_docks to retrieve information from MCP VTEX Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves information about docks (distribution centers or warehouse locations) from the VTEX platform. It has no capability to modify, delete, or execute operations on the infrastructure. The blast radius of misuse is minimal—an agent could only retrieve dock information that already exists in the system, which is informational rather than harmful.
From the tool's definition Tool name 'vtex_list_docks' and description 'List all docks' indicate a retrieval/query operation with no side effects. Docks are logistics/warehouse entities in VTEX inventory management; listing them retrieves configuration data without modification.
Attacks that exploit this kind of access
List all docks. It is categorised as a Read tool in the MCP VTEX Server MCP Server, which means it retrieves data without modifying state.
Register the MCP VTEX Server MCP server in PolicyLayer and add a rule for vtex_list_docks: 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 MCP VTEX Server. Nothing to install.
vtex_list_docks 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 vtex_list_docks 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 vtex_list_docks. 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.
vtex_list_docks is provided by the MCP VTEX Server MCP server (leosepulveda/mcp-vtex). 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 →