fetch_unread_emails
AI agents call fetch_unread_emails to retrieve information from OOSDK MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves email data without side effects. Despite the empty description lowering confidence slightly, the name unambiguously indicates a query operation that retrieves existing unread emails from a mailbox. No data is modified, deleted, or executed. Severity is low as misuse would only expose email content already accessible to the authenticated user, with limited blast radius.
From the tool's definition Tool name 'fetch_unread_emails' clearly indicates a retrieval operation ('fetch') on email data. The action is read-only with no modification, deletion, or execution implied.
Attacks that exploit this kind of access
fetch_unread_emails. It is categorised as a Read tool in the OOSDK MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OOSDK MCP Server MCP server in PolicyLayer and add a rule for fetch_unread_emails: 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 OOSDK MCP Server. Nothing to install.
fetch_unread_emails 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 fetch_unread_emails 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 fetch_unread_emails. 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.
fetch_unread_emails is provided by the OOSDK MCP Server MCP server (sunnylabtv-crypto/ai_mcp_multi_agent_oosdk-public). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →