AI agents call gmail_attachment_metadata to retrieve information from Mcp Gmail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about an email attachment without creating, modifying, or deleting any data. It has no side effects and poses minimal security risk—attachment metadata typically includes filename, size, and MIME type, which are not sensitive enough to warrant higher severity. The 'Get' operation clearly falls under the Read category.
From the tool's definition Tool name 'gmail_attachment_metadata' and description 'Get an attachment' indicate a retrieval operation with no modification capability.
Attacks that exploit this kind of access
Get an attachment. It is categorised as a Read tool in the Mcp Gmail MCP Server, which means it retrieves data without modifying state.
Register the Mcp Gmail MCP server in PolicyLayer and add a rule for gmail_attachment_metadata: 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 Gmail. Nothing to install.
gmail_attachment_metadata 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_attachment_metadata 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_attachment_metadata. 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_attachment_metadata is provided by the Mcp Gmail MCP server (knowledgeislands/mcp-gmail). 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 →