brc_send_email_statement

SERVERRed by Big Red Cloud SOURCEhttps://red.bigredcloud.com/mcp

Medium RISK CLASS

Category Write

Parameters 123 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-bigredcloud-red-mcp-server/brc-send-email-statement.md

WHAT IT DOES

What brc_send_email_statement does on Red by Big Red Cloud

AI agents use brc_send_email_statement to create or update resources in Red by Big Red Cloud, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Red by Big Red Cloud environment.

Parameter	Type	Required	Description
`sendMode`	string	—	How to handle multiple recipients. Use separate only when the user explicitly asks to send separate individual emails.
`toPeriod`	string	—	Statement period end (ISO date-time, e.g. 2026-05-31T00:00:00).
`toAddress`	string	—	Optional single recipient override. If omitted or empty, BRC uses the customer's email address.
`customerId`	integer	Yes	BRC field: customerId.
`fromPeriod`	string	—	Statement period start (ISO date-time, e.g. 2026-01-01T00:00:00).
`minBalance`	number	—	Minimum balance threshold for transactions included on the statement.
`routeToken`	string	Yes	Opaque routeToken from brc_route_request for this action workflow. Required for transactional tools. Routing permission only — does not replace preview-before-p
`companyName`	string	Yes	Company context name, for example YOUR-COMPANY-NAME.
`confirmSend`	boolean	—	Must be true only after the user has reviewed the email preview and explicitly confirmed sending.
`fromAddress`	string	—	Optional sender address override.
`messageBody`	string	—	Optional custom email message body.
`toAddresses`	array	—	Optional list of recipients. If more than one is provided, ask the user whether to send one email with BCC or separate individual emails.

Parameters from the server's own tool schema.

RISK

Why brc_send_email_statement is rated Medium

An AI agent can call brc_send_email_statement faster than any human can review: one bad instruction and it creates or modifies resources in Red by Big Red Cloud by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (14 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs brc_send_email_statement safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Red by Big Red Cloud, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For brc_send_email_statement, this is the rule to start with:

brc_send_email_statement Rate-limited

brc_send_email_statement 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": {
    "brc_send_email_statement": {
      "limits": [
        {
          "counter": "brc_send_email_statement_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Red by Big Red Cloud, apply this rule, and every brc_send_email_statement call is checked against it from then on.

FAQ

Questions about brc_send_email_statement

What does the brc_send_email_statement tool do? +

Sends a customer statement email. Supported document type only. Red email sending is available for sales invoices, quotes, and customer statements — not for cash receipts, purchases, payments, bank accounts, customers, suppliers, products, reports, or other document types. If the user asks to email an unsupported document type, say Red cannot email it through the current MCP tools, list the supported types, and stop without preparing an email preview or attempting a workaround. Do not call this tool with confirmSend=true until the user has reviewed a plain-English email preview and explicitly confirmed they want to send it. The email preview must show the recipient email address clearly before asking for send confirmation. If there is no customer email on file and no recipient override, stop and ask for a recipient email address — do not send. Create/post confirmation and email send confirmation are separate steps. If the user provides multiple recipient addresses, ask whether to send one email using BCC or separate individual emails. Only use sendMode='separate' when the user explicitly chooses separate emails. Do not ask about BCC unless the user provides multiple recipients or asks to copy another address. Requires routeToken from brc_route_request for the matching action workflow. Call brc_route_request first with the user's complete original action request. Retain the returned routeToken through lookup, preview, and confirmation, and pass the same token on the final permitted transactional tool call. Never invent a placeholder token. A routeToken is not permission to post — preview-before-posting and confirmWrite/confirmDelete still apply. It is categorised as a Write tool in the Red by Big Red Cloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does brc_send_email_statement accept? +

brc_send_email_statement accepts 12 parameters: sendMode, toPeriod, toAddress, customerId, fromPeriod, minBalance, routeToken, companyName, confirmSend, fromAddress, messageBody, toAddresses. Required: customerId, routeToken, companyName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on brc_send_email_statement? +

Register the Red by Big Red Cloud MCP server in PolicyLayer and add a rule for brc_send_email_statement: 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 Red by Big Red Cloud. Nothing to install.

What risk level is brc_send_email_statement? +

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

Can I rate-limit brc_send_email_statement? +

Yes. Add a rate_limit block to the brc_send_email_statement 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 brc_send_email_statement completely? +

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

brc_send_email_statement is provided by the Red by Big Red Cloud MCP server (https://red.bigredcloud.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Red by Big Red Cloud, and thousands of servers like it.

This server

All 159 Red by Big Red Cloud tools →

Across the catalogue

send-email on Meme MCP Server →sms_send on Twilio SMS MCP Server →mail_send_draft on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →