Generate pre-built email templates
AI agents use generate_template to create or update resources in MJML MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MJML MCP Server environment.
The tool creates new email template data structures without irreversibly destroying existing data. It is a reversible write operation (templates can be modified or deleted later). There is no code execution, financial transaction, or destructive action. Severity is low because misuse would only result in creation of unwanted template data with minimal blast radius.
From the tool's definition Tool generates 'pre-built email templates' and the server enables 'creation and management of professional email templates.' This is a generative operation that creates new template artifacts.
Attacks that exploit this kind of access
Generate pre-built email templates. It is categorised as a Write tool in the MJML MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MJML MCP Server MCP server in PolicyLayer and add a rule for generate_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 MJML MCP Server. Nothing to install.
generate_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 generate_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 generate_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.
generate_template is provided by the MJML MCP Server MCP server (shaunie2fly/mjml_mcp). 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 →