clasp_clone · Google Apps Script MCP Server MCP

WHAT IT DOES

What clasp_clone does on Google Apps Script MCP Server

AI agents use clasp_clone to create or update resources in Google Apps Script MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Apps Script MCP Server environment.

WHY IT NEEDS A POLICY

Why clasp_clone needs a policy

Cloning creates a new, reversible copy of a project. This is a Write operation—it creates/duplicates data without irreversible destruction. The severity is medium because while the cloned project itself is benign, a compromised agent could clone sensitive proprietary projects, exfiltrate code, or create unauthorized copies.

From the tool's definition Tool name 'clasp_clone' and description indicate cloning/copying an existing Google Apps Script project. The Japanese description translates to 'Clone an existing Google Apps Script project.' This creates a new copy of project data (files, configurations).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

clasp_clone Rate-limited

clasp_clone 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": {
    "clasp_clone": {
      "limits": [
        {
          "counter": "clasp_clone_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Google Apps Script MCP Server, so you can run agents against it safely.

FAQ

Questions about clasp_clone

What does the clasp_clone tool do? +

既存のGoogle Apps Scriptプロジェクトをクローンします. It is categorised as a Write tool in the Google Apps Script MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on clasp_clone? +

Register the Google Apps Script MCP Server MCP server in PolicyLayer and add a rule for clasp_clone: 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 Google Apps Script MCP Server. Nothing to install.

What risk level is clasp_clone? +

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

Can I rate-limit clasp_clone? +

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

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

clasp_clone is provided by the Google Apps Script MCP Server MCP server (utakata/google-apps-script-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.