Account-wide pool snapshot: used_bytes, limit_bytes, addon size, addon active/grace flags. Useful before initiating a large upload.
AI agents call drive_storage_summary 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.
This tool reads and returns account-wide storage statistics (used bytes, limit bytes, addon size, flags). It is a read-only query used to inform decisions before uploading, with no write, execute, or destructive capabilities. Misuse risk is minimal as it only exposes storage metadata.
From the tool's definition 'pool snapshot: used_bytes, limit_bytes, addon size, addon active/grace flags' — purely retrieves storage metrics with no side effects
Attacks that exploit this kind of access
Account-wide pool snapshot: used_bytes, limit_bytes, addon size, addon active/grace flags. Useful before initiating a large upload. 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_storage_summary: 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_storage_summary 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_storage_summary 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_storage_summary. 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_storage_summary 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.
drive_storage_summary is one line of TrekMail MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →