Low Risk

get-received-email-attachment

Retrieve details of a specific attachment from a received email, including a time-limited download URL.

How to control get-received-email-attachment ↓

AI agents call get-received-email-attachment to retrieve information from Email Sending MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The tool retrieves metadata and provides access to an attachment via a download URL. There are no side effects, modifications to data, code execution, or destructive operations. While the attachment content itself could theoretically be sensitive, the tool's function is purely informational retrieval. The time-limited URL is a security best practice.

From the tool's definition Tool performs a retrieval operation: 'Retrieve details of a specific attachment from a received email, including a time-limited download URL.' This is a read-only query with no modification, deletion, or execution of code.

Documented attack patterns abuse exactly the kind of access get-received-email-attachment gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Email Sending MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get-received-email-attachment:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-received-email-attachment": {}
  }
}

get-received-email-attachment is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Email Sending MCP — 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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get-received-email-attachment tool do? +

Retrieve details of a specific attachment from a received email, including a time-limited download URL. It is categorised as a Read tool in the Email Sending MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-received-email-attachment? +

Register the Email Sending MCP server in PolicyLayer and add a rule for get-received-email-attachment: 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 Email Sending MCP. Nothing to install.

What risk level is get-received-email-attachment? +

get-received-email-attachment is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-received-email-attachment? +

Yes. Add a rate_limit block to the get-received-email-attachment 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 get-received-email-attachment completely? +

Set action: deny in the PolicyLayer policy for get-received-email-attachment. 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 get-received-email-attachment? +

get-received-email-attachment is provided by the Email Sending MCP server (resend/resend-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Email Sending MCP tool call.

Deterministic rules across all 77 Email Sending MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

77 Email Sending MCP tools catalogued and risk-classified — across an index of 42,500+ 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.