mail_send
Send a test email to verify mail configuration is working. Provide a subject, body text, and one or more recipient addresses.
This record as markdown: /tools/nasbridge/mail-send.md
What mail_send does on Nasbridge
AI agents invoke mail_send to trigger actions in Nasbridge. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why mail_send is rated High
This tool triggers an external operation (sending an email) whose effects depend on arguments (subject, body, recipients). It does not simply read or write data within the system—it causes an external side effect by delivering email to specified recipients. Misuse could lead to spam or phishing emails being sent to arbitrary addresses.
From the tool's definition Send a test email to verify mail configuration is working. Provide a subject, body text, and one or more recipient addresses.
Attacks that exploit this kind of access
The rule that runs mail_send safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mail_send, this is the rule to start with:
mail_send stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every mail_send call is checked against it from then on.
Questions about mail_send
Send a test email to verify mail configuration is working. Provide a subject, body text, and one or more recipient addresses. It is categorised as a Execute tool in the Nasbridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nasbridge MCP server in PolicyLayer and add a rule for mail_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 Nasbridge. Nothing to install.
mail_send is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mail_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.
Set action: deny in the PolicyLayer policy for mail_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.
mail_send is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
Across the catalogue