drive_share

Mint a scoped drive access token for another agent (perms read|write, optional path prefix + TTL like 7d). The secret is returned ONCE.

SERVERMcp SOURCEhttps://dataecho.ai/mcp
Medium RISK CLASS
Category Write
Parameters 51 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What drive_share does on Mcp

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

ParameterTypeRequiredDescription
ttl string Lifetime, e.g. 1h, 7d (omit for no expiry)
drive string Yes Drive name or drv_… id
label string Human label for the token
perms string read (default) or write
pathPrefix string Restrict the token to this path prefix

Parameters from the server's own tool schema.

Why drive_share is rated Medium

This tool creates (mints) new security credentials that grant another agent read or write access to a drive. While not destructive, it modifies the access control state by issuing a new token with specific permissions.

From the tool's definition Tool description: 'Mint a scoped drive access token for another agent (perms read|write, optional path prefix + TTL like `7d`). The secret is returned ONCE.' — creates and returns access credentials.

Questions about drive_share

What does the drive_share tool do? +

Mint a scoped drive access token for another agent (perms read|write, optional path prefix + TTL like 7d). The secret is returned ONCE. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does drive_share accept? +

drive_share accepts 5 parameters: ttl, drive, label, perms, pathPrefix. 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_share? +

Register the MCP server in PolicyLayer and add a rule for drive_share: 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_share? +

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

Can I rate-limit drive_share? +

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

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

drive_share 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.