drive_space_usage

Per-space quota snapshot. Same numbers as storage_summary but tagged to the resolved space.

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-space-usage.md

WHAT IT DOES

What drive_space_usage does on TrekMail MCP Server

AI agents call drive_space_usage 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_space_usage is rated Low

This tool retrieves storage/quota usage data (a read-only snapshot). It has no side effects, does not modify data, and is purely informational. Severity is low as misuse only exposes storage usage metrics.

From the tool's definition Per-space quota snapshot. Same numbers as storage_summary but tagged to the resolved space.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs drive_space_usage 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_space_usage, this is the rule to start with:

drive_space_usage Allowed

drive_space_usage 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_space_usage": {}
  }
}

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_space_usage call is checked against it from then on.

FAQ

Questions about drive_space_usage

What does the drive_space_usage tool do? +

Per-space quota snapshot. Same numbers as storage_summary but tagged to the resolved space. 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_space_usage? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for drive_space_usage: 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_space_usage? +

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

Can I rate-limit drive_space_usage? +

Yes. Add a rate_limit block to the drive_space_usage 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_space_usage completely? +

Set action: deny in the PolicyLayer policy for drive_space_usage. 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_space_usage? +

drive_space_usage 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 →