sf_send_email

Sends an email from Salesforce using the emailSimple invocable action. The email is sent from the running user

SERVERSalesforce Metadata Mcp SOURCEsalesforce-metadata-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-send-email.md

What sf_send_email does on Salesforce Metadata Mcp

AI agents invoke sf_send_email to trigger actions in Salesforce Metadata Mcp. 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 sf_send_email is rated High

This tool triggers an external operation (sending an email) that has real-world effects — recipients receive messages that cannot be unsent. While not financial or destructive to data, it executes an irreversible external action (email delivery) with significant blast radius if misused by an AI agent, e.g., sending spam, phishing, or sensitive data to unintended recipients.

From the tool's definition Sends an email from Salesforce using the emailSimple invocable action

Questions about sf_send_email

What does the sf_send_email tool do? +

Sends an email from Salesforce using the emailSimple invocable action. The email is sent from the running user. It is categorised as a Execute tool in the Salesforce Metadata Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sf_send_email? +

Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_send_email: 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 Salesforce Metadata Mcp. Nothing to install.

What risk level is sf_send_email? +

sf_send_email is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sf_send_email? +

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

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

sf_send_email is provided by the Salesforce Metadata MCP server (salesforce-metadata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Salesforce Metadata, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Salesforce Metadata's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.