email_scaffold_send · LaunchFrame MCP: Risk & Policy

WHAT IT DOES

What email_scaffold_send does on LaunchFrame MCP

AI agents use email_scaffold_send 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.

WHY IT NEEDS A POLICY

Why email_scaffold_send needs a policy

This tool generates code that sends emails, which is a write operation that modifies external state (sends messages to mail service). It is not destructive because sending an email is reversible in principle (can be unsent/recalled, and does not permanently delete data). It is not financial, execute, or read.

From the tool's definition Tool description: 'Generate NestJS code to send a transactional email — either by injecting MailService directly (direct) or via the emails Bull queue (queued).' The verb 'send' combined with 'transactional email' indicates the tool creates and transmits…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

email_scaffold_send Rate-limited

email_scaffold_send 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "email_scaffold_send": {
      "limits": [
        {
          "counter": "email_scaffold_send_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LaunchFrame MCP, so you can run agents against it safely.

FAQ

Questions about email_scaffold_send

What does the email_scaffold_send tool do? +

Generate NestJS code to send a transactional email — either by injecting MailService directly (direct) or via the emails Bull queue (queued). 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.

How do I enforce a policy on email_scaffold_send? +

Register the LaunchFrame MCP server in PolicyLayer and add a rule for email_scaffold_send: 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.

What risk level is email_scaffold_send? +

email_scaffold_send is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit email_scaffold_send? +

Yes. Add a rate_limit block to the email_scaffold_send 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.

How do I block email_scaffold_send completely? +

Set action: deny in the PolicyLayer policy for email_scaffold_send. 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.

What MCP server provides email_scaffold_send? +

email_scaffold_send 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.