drive_share_revoke

Revoke a share-link by id. Idempotent — second call no-ops.

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/drive-share-revoke.md

WHAT IT DOES

What drive_share_revoke does on TrekMail MCP Server

AI agents call drive_share_revoke to permanently remove resources in TrekMail MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why drive_share_revoke is rated Critical

Revoking a share link removes access permissions permanently. While noted as idempotent (second call no-ops), the initial revocation is a destructive, non-reversible action that eliminates access for all users relying on that share link. This could have a high blast radius if an AI agent mistakenly revokes widely-used share links.

From the tool's definition Revoke a share-link by id — 'revoke' indicates an irreversible removal of access; once revoked, shared access is eliminated

Attacks that exploit this kind of access

RECOMMENDED RULE

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

drive_share_revoke Hidden

drive_share_revoke is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "drive_share_revoke"
  ]
}

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

FAQ

Questions about drive_share_revoke

What does the drive_share_revoke tool do? +

Revoke a share-link by id. Idempotent — second call no-ops. It is categorised as a Destructive tool in the TrekMail MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on drive_share_revoke? +

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

drive_share_revoke is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit drive_share_revoke? +

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

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

drive_share_revoke 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 → Critical-risk tools on this server →

Across the catalogue

web3_revoke_key on 0xarchive →revoke_api_token on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →