Low Risk

read_email

Read the full content of a specific email.

How to control read_email ↓

What read_email does on MCP Personal Assistant Agent

AI agents call read_email to retrieve information from MCP Personal Assistant Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why read_email needs a policy

This tool retrieves and queries email content without side effects. It does not create, modify, delete, or execute operations. The blast radius is minimal since misuse results only in unauthorized information access to existing emails, not data destruction or external execution.

From the tool's definition Tool name is 'read_email' and description states 'Read the full content of a specific email' — explicitly a retrieval operation with no modification or deletion.

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

How to control read_email

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "read_email": {}
  }
}

read_email 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 MCP Personal Assistant Agent — 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.

Related tools and policies

Go deeper

Questions about read_email

What does the read_email tool do? +

Read the full content of a specific email. It is categorised as a Read tool in the MCP Personal Assistant Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on read_email? +

Register the MCP Personal Assistant Agent MCP server in PolicyLayer and add a rule for read_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 MCP Personal Assistant Agent. Nothing to install.

What risk level is read_email? +

read_email is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit read_email? +

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

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

read_email is provided by the MCP Personal Assistant Agent MCP server (zhangzhongnan928/mcp-pa-ai-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Personal Assistant Agent tool call.

Start from MCP Personal Assistant Agent, 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.

19 MCP Personal Assistant Agent 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.