Generate a Handlebars (.hbs) template stub for a new LaunchFrame transactional email, following project conventions.
AI agents use email_scaffold_template to create or update resources in LaunchFrame MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LaunchFrame MCP environment.
This tool generates (creates) a new file — a Handlebars template stub — following project conventions. It produces a new artifact on disk or in the project, which is a Write action. It does not execute code, delete anything, or involve financial operations.
From the tool's definition Generate a Handlebars (.hbs) template stub for a new LaunchFrame transactional email
Attacks that exploit this kind of access
Generate a Handlebars (.hbs) template stub for a new LaunchFrame transactional email, following project conventions. It is categorised as a Write tool in the LaunchFrame MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LaunchFrame MCP server in PolicyLayer and add a rule for email_scaffold_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 LaunchFrame MCP. Nothing to install.
email_scaffold_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 email_scaffold_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 email_scaffold_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.
email_scaffold_template is provided by the LaunchFrame MCP server (launchframe-dev/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 →