clone_document

SERVEREasyBits SOURCE@easybits.cloud/mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cloud-easybits-easybits/clone-document.md

WHAT IT DOES

What clone_document does on EasyBits

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

RISK

Why clone_document is rated Medium

Creates new document reversibly via AI vision processing without destructive or irreversible effects.

From the tool's definition Clone document, creates NEW document, does not mutate existing

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clone_document safely

PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clone_document, this is the rule to start with:

clone_document Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clone_document": {
      "limits": [
        {
          "counter": "clone_document_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about clone_document

What does the clone_document tool do? +

Clone or reimagine a document from any visual source (image, PDF, or another EasyBits document) using Gemini Vision. Outputs a NEW document (Landing v4) — does not mutate any existing one. SOURCE — pass exactly one shape: - { type:. It is categorised as a Write tool in the EasyBits MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on clone_document? +

Register the EasyBits MCP server in PolicyLayer and add a rule for clone_document: 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 EasyBits. Nothing to install.

What risk level is clone_document? +

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

Can I rate-limit clone_document? +

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

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

clone_document is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EasyBits, and thousands of servers like it.

This server

All 273 EasyBits tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →