drive_tokens

List active share tokens of a drive (secrets are never shown again).

SERVERMcp SOURCEhttps://dataecho.ai/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-dataecho-mcp/drive-tokens.md

WHAT IT DOES

What drive_tokens does on Mcp

AI agents call drive_tokens to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`drive`	string	Yes	Drive name or drv_… id

Parameters from the server's own tool schema.

RISK

Why drive_tokens is rated Low

The tool retrieves and enumerates metadata about existing share tokens on a drive. While tokens themselves can be sensitive, this tool only reads/lists their existence and metadata without creating, modifying, deleting, or executing operations. The description explicitly states 'secrets are never shown again,' confirming that sensitive token values are not exposed.

From the tool's definition Tool name contains 'list' operation pattern and description says "List active share tokens of a drive"; the verb 'List' indicates retrieval without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

drive_tokens Allowed

drive_tokens is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "drive_tokens": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every drive_tokens call is checked against it from then on.

FAQ

Questions about drive_tokens

What does the drive_tokens tool do? +

List active share tokens of a drive (secrets are never shown again). It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does drive_tokens accept? +

drive_tokens accepts 1 parameter: drive. Required: drive. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on drive_tokens? +

Register the MCP server in PolicyLayer and add a rule for drive_tokens: 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.

What risk level is drive_tokens? +

drive_tokens is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit drive_tokens? +

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

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

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

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 26 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →