drive_folder_stop_sharing · TrekMail MCP Server MCP

WHAT IT DOES

What drive_folder_stop_sharing does on TrekMail MCP Server

AI agents use drive_folder_stop_sharing to create or update resources in TrekMail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TrekMail MCP Server environment.

WHY IT NEEDS A POLICY

Why drive_folder_stop_sharing needs a policy

This tool modifies the sharing state of a folder (reversibly changing is_shared to false). The folder is not deleted — it remains in the account-drive as a private folder. Since data is not destroyed and the action could be reversed by re-enabling sharing, this is a Write operation.

From the tool's definition Flip is_shared back to false on a shared folder... other mailboxes lose visibility, the dashboard owner keeps it as a private account-drive folder.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drive_folder_stop_sharing Rate-limited

drive_folder_stop_sharing stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "drive_folder_stop_sharing": {
      "limits": [
        {
          "counter": "drive_folder_stop_sharing_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TrekMail MCP Server, so you can run agents against it safely.

FAQ

Questions about drive_folder_stop_sharing

What does the drive_folder_stop_sharing tool do? +

Flip is_shared back to false on a shared folder. Folder stays in account-drive (no migration back to a specific mailbox); other mailboxes lose visibility, the dashboard owner keeps it as a private account-drive folder. Idempotent on already-private folders. It is categorised as a Write tool in the TrekMail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on drive_folder_stop_sharing? +

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

drive_folder_stop_sharing is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit drive_folder_stop_sharing? +

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

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

drive_folder_stop_sharing 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.