Get a document from Master Data
AI agents call vtex_get_document 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 retrieves data from VTEX Master Data without modifying, deleting, or executing operations. It is a pure read operation. Severity is low because retrieving documents from a data store has limited blast radius unless the documents contain highly sensitive personal or financial data, but the tool itself does not expose that sensitivity—it is the nature of what is stored that matters, and read-only access is…
From the tool's definition Tool name is 'vtex_get_document' and description states 'Get a document from Master Data' - the verb 'Get' and operation 'retrieve from' indicate a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
Get a document from Master Data. 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_get_document: 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_get_document 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_get_document 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_get_document. 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_get_document 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 →