drive_addon_get
Current Drive Storage Add-on state: active flag, in_grace, size_gb, period end, hard-delete date if cancelled.
This record as markdown: /tools/trekmail-mcp-server/drive-addon-get.md
What drive_addon_get does on TrekMail MCP Server
AI agents call drive_addon_get 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.
Why drive_addon_get is rated Low
This tool queries the current status of a Drive storage add-on subscription without modifying, deleting, or executing any operations. It returns read-only state information (flags, sizes, dates) useful for monitoring and informational purposes. No destructive, financial, or executable actions are performed.
From the tool's definition Tool name 'drive_addon_get' and description indicate retrieval of storage add-on state information: 'active flag, in_grace, size_gb, period end, hard-delete date if cancelled.' The verb 'get' and the passive voice describing state attributes confirm this is a…
Attacks that exploit this kind of access
The rule that runs drive_addon_get 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_addon_get, this is the rule to start with:
drive_addon_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every drive_addon_get call is checked against it from then on.
Questions about drive_addon_get
Current Drive Storage Add-on state: active flag, in_grace, size_gb, period end, hard-delete date if cancelled. 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_addon_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_addon_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_addon_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_addon_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_addon_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.
More on TrekMail MCP Server, and thousands of servers like it.
This server
Across the catalogue