This record as markdown: /tools/ai-dataecho-mcp/drive-revoke-token.md
What drive_revoke_token does on Mcp
AI agents call drive_revoke_token to permanently remove resources in Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
drive | string | Yes | Drive name or drv_… id |
tokenId | string | Yes | dtok_… id from drive_tokens |
Parameters from the server's own tool schema.
Why drive_revoke_token is rated Critical
Revoking a share token is an irreversible action that permanently invalidates access credentials. Any users or systems relying on that token will immediately lose access and the token cannot be un-revoked, making this a destructive operation with potentially high blast radius if an agent misuses it by cutting off legitimate access to shared drives.
From the tool's definition Revoke a drive share token
Attacks that exploit this kind of access
The rule that runs drive_revoke_token safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For drive_revoke_token, this is the rule to start with:
drive_revoke_token is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every drive_revoke_token call is checked against it from then on.
Questions about drive_revoke_token
Revoke a drive share token. It is categorised as a Destructive tool in the Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
drive_revoke_token accepts 2 parameters: drive, tokenId. Required: drive, tokenId. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for drive_revoke_token: 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 Mcp. Nothing to install.
drive_revoke_token is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the drive_revoke_token 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_revoke_token. 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_revoke_token is provided by the MCP server (https://dataecho.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue