Skip to main content
Glama
googlarz

Proton Drive MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Revoke member access

drive_share_revoke
Destructive

Remove one person's access to a shared Proton Drive file or folder without notifying them. Confirm the email with drive_share_status first; fails if not a current member or invitee.

Instructions

Remove one person's access (accepted or pending) to a Proton Drive file or folder; they are not notified. Fails if the address is not a current member or invitee (case-insensitive match). Confirm the email with drive_share_status first. To change a role, revoke and re-invite. To remove everyone use drive_share_remove_all. Requires confirmed=true after explicit user approval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute remote path of the shared item, as used when inviting.
emailYesEmail of the member to remove, as shown by drive_share_status.
confirmedNoMust be true; only after the user approved this exact action.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.0
    • changedInput schema / properties / confirmed / description
      Previous value: -"Must be true. Only set after the user explicitly approved this exact action."New value: +"Must be true; only after the user approved this exact action."
    • changedInput schema / properties / email / description
      Previous value: -"Email address of the member to remove. Must exactly match the address shown by drive_share_status — use drive_share_status first to confirm. E.g. alice@example.com."New value: +"Email of the member to remove, as shown by drive_share_status."
    • changedInput schema / properties / path / description
      Previous value: -"Absolute remote Drive path of the shared file or folder (must start with '/'). E.g. /my-files/project. Must match the path used when the invitation was sent."New value: +"Absolute remote path of the shared item, as used when inviting."
  2. Changed1 schema field changedv1.0.38
    • addedInput schema / properties / confirmed
      Added value: +{
+  "description": "Must be true. Only set after the user explicitly approved this exact action.",
+  "type": "boolean"
+}
  3. Changed2 schema fields changedv1.0.23
    • changedInput schema / properties / email / description
      Previous value: -"Email address of the person whose access to revoke."New value: +"Email address of the member to remove. Must exactly match the address shown by drive_share_status — use drive_share_status first to confirm. E.g. alice@example.com."
    • changedInput schema / properties / path / description
      Previous value: -"Absolute remote Drive path (must start with '/')."New value: +"Absolute remote Drive path of the shared file or folder (must start with '/'). E.g. /my-files/project. Must match the path used when the invitation was sent."
  4. Changed1 schema field changedv0.1.2
    • changedInput schema / properties / path / description
      Previous value: -"Remote Drive path."New value: +"Absolute remote Drive path (must start with '/')."
  5. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only supply destructiveHint=true, and the description adds substantial context beyond that: the target is not notified, pending invites are included, the operation fails on a non-member address (case-insensitive match), and confirmed=true is required only after explicit user approval. This is exactly the behavioral disclosure a destructive mutation needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short sentences, front-loaded with the action and scope, then prerequisites, then alternatives. Every sentence carries a distinct decision-relevant fact; nothing is redundant with the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, no-output-schema mutation with thin annotations, the description covers what is destroyed (one member's access), what is not (no notification), failure modes, prerequisites, and the approval gate. Nothing needed to invoke it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the email must correspond to a current member or invitee (case-insensitive) and 'confirmed' is a deliberate user-approval gate rather than a plain boolean. Format details for path remain with the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — removing one person's access to a Proton Drive file or folder — and immediately scopes it to 'one person,' which separates it from drive_share_remove_all and drive_share_leave. An agent can select it correctly without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: verify the address with drive_share_status first, use drive_share_remove_all to remove everyone, and revoke-plus-re-invite to change a role. Both prerequisites and alternatives are named, with the condition that selects each.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools