This record as markdown: /tools/ai-dataecho-mcp/create-drive.md
What create_drive does on Mcp
AI agents use create_drive 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Drive name |
Parameters from the server's own tool schema.
Why create_drive is rated Medium
This tool creates a new persistent storage resource ('private drive') for the agent. Creation is reversible (the sibling tool 'drive_delete_file' and 'delete_site' suggest deletion capabilities exist), so it is Write rather than Destructive.
From the tool's definition Tool name is 'create_drive' and description states it will 'Create a new private drive' – a creation action that modifies the agent's state by adding a new storage resource.
Attacks that exploit this kind of access
The rule that runs create_drive 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 create_drive, this is the rule to start with:
create_drive stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every create_drive call is checked against it from then on.
Questions about create_drive
Create a new private drive. 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.
create_drive accepts 1 parameter: name. Required: name. 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 create_drive: 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.
create_drive is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_drive 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 create_drive. 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.
create_drive 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