get-received-email-attachment

// WHEN AI AGENTS USE THIS TOOL

AI agents call get-received-email-attachment to retrieve information from Resend without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON GET-RECEIVED-EMAIL-ATTACHMENT

Even though get-received-email-attachment only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

resend.yaml

tools:
  get-received-email-attachment:
    rules:
      - action: allow

See the full Resend policy for all 44 tools.

// DETAILS

Tool Name get-received-email-attachment

Category Read

MCP Server Resend MCP Server

Risk Level Low

// MORE RESEND TOOLS

Destructive cancel-email Destructive remove-api-key Destructive remove-broadcast Destructive remove-contact Destructive remove-segment Destructive remove-topic Write create-api-key Write create-broadcast

View all 44 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like get-received-email-attachment have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

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

Download a received email attachment. It is categorised as a Read tool in the Resend MCP Server, which means it retrieves data without modifying state.

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

Add a rule in your Intercept YAML policy under the tools section for get-received-email-attachment. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Resend MCP server.

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 Intercept 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 Intercept 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 Resend MCP server (@resend-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Resend