Return full email content (plain text preferred).
AI agents call gmail_get_message to retrieve information from AIOS Co-Founder MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and returns email content without modifying, deleting, or executing any actions. It is a pure read operation on Gmail data. Severity is low because email content retrieval, while it may expose sensitive information, does not directly cause harm or enable further damaging actions without additional tools. An AI misusing this tool would be able to read emails but not send, delete, or act on them.
From the tool's definition Tool name is 'gmail_get_message' and description states 'Return full email content (plain text preferred).' This is a retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Return full email content (plain text preferred). It is categorised as a Read tool in the AIOS Co-Founder MCP MCP Server, which means it retrieves data without modifying state.
Register the AIOS Co-Founder MCP server in PolicyLayer and add a rule for gmail_get_message: 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 AIOS Co-Founder MCP. Nothing to install.
gmail_get_message 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 gmail_get_message 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 gmail_get_message. 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.
gmail_get_message is provided by the AIOS Co-Founder MCP server (varun-b-nagaraj/python-mcp-server). 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 →