email_move_messages

Move emails between folders by UID.

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-move-messages.md

WHAT IT DOES

What email_move_messages does on Freshdesk

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

This tool modifies email organization by relocating messages between folders. While reversible (emails can be moved back), it alters data state and could disrupt ticket organization or workflows if misused by an AI agent.

From the tool's definition Tool description states 'Move emails between folders by UID.' Moving emails is a reversible modification operation that reorganizes data without deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

email_move_messages Rate-limited

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

FAQ

Questions about email_move_messages

What does the email_move_messages tool do? +

Move emails between folders by UID. 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_move_messages? +

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

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

Can I rate-limit email_move_messages? +

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

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

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