File metadata: name, size, mime, status, scan status, has_active_share_link.
AI agents call drive_file_get to retrieve information from TrekMail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
drive_file_get performs a simple metadata query operation without side effects. It only retrieves and returns file information properties, making it a Read category tool. The metadata exposed (name, size, MIME type, status fields) poses minimal risk even if an agent queries files it shouldn't, since no data is modified, deleted, or executed. Severity is low given the read-only nature and limited blast radius.
From the tool's definition Tool retrieves 'File metadata: name, size, mime, status, scan status, has_active_share_link' — all read-only attributes with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
File metadata: name, size, mime, status, scan status, has_active_share_link. It is categorised as a Read tool in the TrekMail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for drive_file_get: 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 TrekMail MCP Server. Nothing to install.
drive_file_get 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 drive_file_get 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 drive_file_get. 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.
drive_file_get is provided by the TrekMail MCP Server MCP server (trekmail/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 →