AI agents use update-email-template to create or update resources in SMTP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SMTP MCP Server environment.
This tool modifies existing email templates reversibly. While it changes data, the modification is not destructive (the old template is not permanently deleted, just replaced). The severity is medium because misuse could lead to sending unintended email content to recipients via the bulk sending capabilities, but the change itself is reversible by updating the template again.
From the tool's definition Tool is named 'update-email-template' and described as 'Update an existing email template', indicating modification of existing data. The server context shows this is part of an email/SMTP system where templates are used for bulk email sending.
Documented attack patterns abuse exactly the kind of access update-email-template gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SMTP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update-email-template:
{
"version": "1",
"default": "deny",
"tools": {
"update-email-template": {
"limits": [
{
"counter": "update-email-template_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-email-template stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update an existing email template. It is categorised as a Write tool in the SMTP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SMTP MCP Server MCP server in PolicyLayer and add a rule for update-email-template: 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 SMTP MCP Server. Nothing to install.
update-email-template is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update-email-template 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 update-email-template. 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.
update-email-template is provided by the SMTP MCP Server MCP server (samihalawa/mcp-server-smtp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SMTP MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 SMTP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.