drive_storage_summary

Account-wide pool snapshot: used_bytes, limit_bytes, addon size, addon active/grace flags. Useful before initiating a large upload.

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/drive-storage-summary.md

WHAT IT DOES

What drive_storage_summary does on TrekMail MCP Server

AI agents call drive_storage_summary to retrieve information from TrekMail MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why drive_storage_summary is rated Low

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

RECOMMENDED RULE

The rule that runs drive_storage_summary safely

PolicyLayer is an MCP gateway: it sits between your AI agents and TrekMail MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For drive_storage_summary, this is the rule to start with:

drive_storage_summary Allowed

drive_storage_summary is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "drive_storage_summary": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every drive_storage_summary call is checked against it from then on.

FAQ

Questions about drive_storage_summary

What does the drive_storage_summary tool do? +

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.

How do I enforce a policy on drive_storage_summary? +

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.

What risk level is drive_storage_summary? +

drive_storage_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit drive_storage_summary? +

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.

How do I block drive_storage_summary completely? +

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.

What MCP server provides drive_storage_summary? +

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.

KEEP EXPLORING

More on TrekMail MCP Server, and thousands of servers like it.

This server

All 248 TrekMail MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →