move_email

Move an email to a different folder.

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

WHAT IT DOES

What move_email does on Freshdesk

AI agents use move_email 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 move_email is rated Medium

Moving an email to a different folder is a reversible write operation that modifies the organizational state of data. It does not delete data (which would be Destructive), nor does it execute arbitrary code (Execute), nor does it retrieve data (Read).

From the tool's definition Tool name 'move_email' and description 'Move an email to a different folder' indicates modification of email state/location without deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

move_email Rate-limited

move_email 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": {
    "move_email": {
      "limits": [
        {
          "counter": "move_email_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 move_email call is checked against it from then on.

FAQ

Questions about move_email

What does the move_email tool do? +

Move an email to a different folder. 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 move_email? +

Register the Freshdesk MCP server in PolicyLayer and add a rule for move_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 move_email? +

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

Can I rate-limit move_email? +

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

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

move_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 →

Across the catalogue

move-task on Kanban MCP Server →forward-email on Meme MCP Server → The MCP Attack Database →

Guides

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