Send an email using template
AI agents invoke vtex_send_email to trigger actions in MCP VTEX Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Sending an email is an external operation with real-world effects (delivering messages to recipients). It is not merely writing internal data but executing an action that reaches outside the system. Misuse could result in sending spam, phishing, or unauthorized communications to customers at scale, making severity high.
From the tool's definition 'Send an email using template' — triggers an external email operation to real recipients
Attacks that exploit this kind of access
Send an email using template. It is categorised as a Execute tool in the MCP VTEX Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP VTEX Server MCP server in PolicyLayer and add a rule for vtex_send_email: 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_send_email is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the vtex_send_email 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_send_email. 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_send_email 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 →