# reply_to_email

Reply to an email (sender only).

Agent View of the PolicyLayer registry record for `reply_to_email`. HTML page: https://policylayer.com/tools/0xka13b-microsoft-mcps/reply-to-email

## Facts

- Tool: `reply_to_email`
- Server: Microsoft MCP (`0xka13b/microsoft-mcps`) — https://policylayer.com/tools/0xka13b-microsoft-mcps.md
- Homepage: https://github.com/0xka13b/microsoft-mcps
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 3 (2 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `body` | string | yes | Reply body |
| `email_id` | string | yes | Message ID to reply to |
| `body_type` | string | no | Body content type. Defaults to text. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "reply_to_email",
    "arguments": {
      "body": "<body>",
      "email_id": "<email_id>"
    }
  }
}
```

## Why reply_to_email is rated Medium

Replying to an email creates a new outbound message, which is a reversible write/create operation. It does not delete data, execute code, or involve financial transactions. The blast radius is medium because an AI agent could send unintended or sensitive replies to external parties on the user's behalf.

From the tool's own definition: "'Reply to an email (sender only)' — creates a new reply message directed to the original sender"

Risk signals: Accepts raw HTML/template content (body)

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Microsoft MCP:

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

## Other tools on Microsoft MCP (13)

- `delete_email` — Destructive — https://policylayer.com/tools/0xka13b-microsoft-mcps/delete-email.md
- `get_attachment` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/get-attachment.md
- `get_email` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/get-email.md
- `list_emails` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/list-emails.md
- `me` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/me.md
- `search_emails` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/search-emails.md
- `unified_search` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/unified-search.md
- `create_email_draft` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/create-email-draft.md
- `create_reply_draft` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/create-reply-draft.md
- `move_email` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/move-email.md
- `reply_all_email` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/reply-all-email.md
- `send_email` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/send-email.md
- `update_email` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/update-email.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0xka13b-microsoft-mcps · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xka13b-microsoft-mcps
