High Risk →

reply_to_email

Reply to an email message.

How to control reply_to_email ↓

What reply_to_email does on Apple Shortcuts

AI agents invoke reply_to_email to trigger actions in Apple Shortcuts. 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.

High Risk

Why reply_to_email needs a policy

Replying to an email triggers an external operation (sending an email), which is an irreversible action with real-world communication side effects. This goes beyond a simple write as it interacts with external parties. The tool appears to be implemented via Apple Shortcuts/macOS CLI, making it an execution of an external operation. Severity is high because a misused AI agent could send unintended emails to contacts.

From the tool's definition Reply to an email message

Documented attack patterns abuse exactly the kind of access reply_to_email gives an agent:

How to control reply_to_email

PolicyLayer is an MCP gateway — it sits between your AI agents and Apple Shortcuts, and nothing reaches the server without passing your rules. This is the rule we recommend for reply_to_email:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "reply_to_email": {
      "limits": [
        {
          "counter": "reply_to_email_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Apple Shortcuts — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about reply_to_email

What does the reply_to_email tool do? +

Reply to an email message. It is categorised as a Execute tool in the Apple Shortcuts MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reply_to_email? +

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

What risk level is reply_to_email? +

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

Can I rate-limit reply_to_email? +

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

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

reply_to_email is provided by the Apple Shortcuts MCP server (@mindstone/mcp-server-apple-shortcuts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Apple Shortcuts tool call.

Start from Apple Shortcuts, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

423 Apple Shortcuts tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.