forward_email

Forward an email to other recipients.

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

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/freshdesk/forward-email.md

WHAT IT DOES

What forward_email does on Freshdesk

AI agents invoke forward_email to trigger actions in Freshdesk. 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.

RISK

Why forward_email is rated High

Forwarding an email triggers an external operation (sending an email to new recipients), which is an irreversible action with real-world side effects. It doesn't just read or write data internally — it dispatches communication externally. This could leak sensitive support ticket information to unintended parties if misused, making severity high.

From the tool's definition Forward an email to other recipients

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs forward_email 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 forward_email, this is the rule to start with:

forward_email Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "forward_email": {
      "limits": [
        {
          "counter": "forward_email_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every forward_email call is checked against it from then on.

FAQ

Questions about forward_email

What does the forward_email tool do? +

Forward an email to other recipients. It is categorised as a Execute tool in the Freshdesk MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on forward_email? +

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

What risk level is forward_email? +

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

Can I rate-limit forward_email? +

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

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

forward_email 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →