email_send

Send an email. For replies, provide reply_to_message_id from the original message.

SERVERFreshdesk SOURCE@mindstone-engineering/mcp-server-freshdesk

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/freshdesk/email-send.md

WHAT IT DOES

What email_send does on Freshdesk

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

RISK

Why email_send is rated Medium

Sending emails creates new outbound messages and modifies system state (adding records to mail logs, affecting recipient inboxes). While reversible in principle (emails can be deleted from drafts or recipient inboxes), once sent, the action cannot be fully undone.

From the tool's definition Tool is named 'email_send' and described as 'Send an email.' This creates new email messages, a form of data creation/modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs email_send safely

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

email_send Rate-limited

email_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_send": {
      "limits": [
        {
          "counter": "email_send_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 Freshdesk, apply this rule, and every email_send call is checked against it from then on.

FAQ

Questions about email_send

What does the email_send tool do? +

Send an email. For replies, provide reply_to_message_id from the original message. It is categorised as a Write tool in the Freshdesk 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_send? +

Register the Freshdesk MCP server in PolicyLayer and add a rule for email_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 Freshdesk. Nothing to install.

What risk level is email_send? +

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

Can I rate-limit email_send? +

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

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

email_send is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Freshdesk, and thousands of servers like it.

This server

All 422 Freshdesk 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 →