Read the full content of an email by message ID. Content is sanitized and filtered for safety.
AI agents call read_email to retrieve information from AgentCloak without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves email content without side effects. Although it accesses potentially sensitive information, the server's safety controls (PII redaction, sanitization, read-only design) mitigate risk. The primary function is data retrieval, placing it in the Read category at low severity.
From the tool's definition Tool name is 'read_email' and description states it 'Read[s] the full content of an email by message ID.' The server is described as having a 'read-only design' with 'PII redaction' and 'sanitization.' No modification, deletion, or execution is performed.
Documented attack patterns abuse exactly the kind of access read_email gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AgentCloak, and nothing reaches the server without passing your rules. This is the rule we recommend for read_email:
{
"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.
Free to start. No card required.
Read the full content of an email by message ID. Content is sanitized and filtered for safety. It is categorised as a Read tool in the AgentCloak MCP Server, which means it retrieves data without modifying state.
Register the AgentCloak 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 AgentCloak. Nothing to install.
read_email is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
read_email is provided by the AgentCloak MCP server (ryanfren/agentcloak). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AgentCloak, 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.
8 AgentCloak tools catalogued and risk-classified — across an index of 43,000+ MCP servers.