AI agents use build_email_template to create or update resources in Moengage — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Moengage environment.
The name implies constructing or creating an email template, which is a Write operation (creating/modifying data reversibly). Confidence is reduced due to the empty description. Given sibling tools like 'create_campaign' and 'analyze_template', this tool likely creates or builds a new email template asset. Severity is medium as misuse could result in unwanted templates being created in the marketing platform.
From the tool's definition Tool name 'build_email_template' suggests creation/modification of an email template; description is empty and uninformative.
Attacks that exploit this kind of access
build_email_template. It is categorised as a Write tool in the Moengage MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Moengage MCP server in PolicyLayer and add a rule for build_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 Moengage. Nothing to install.
build_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 build_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 build_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.
build_email_template is provided by the Moengage MCP server (poddubnyoleg/moengage_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 →