clasp_pull · Google Apps Script MCP Server MCP

WHAT IT DOES

What clasp_pull does on Google Apps Script MCP Server

AI agents use clasp_pull 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_pull needs a policy

A 'clasp pull' operation fetches remote Google Apps Script files and writes them to the local filesystem, potentially overwriting existing local files. This is a Write operation (modifying local files) rather than pure Read, since it changes the local project state. It is not Destructive in the irreversible sense as the remote source remains intact, but local unsaved changes could be lost.

From the tool's definition 「リモートの変更をローカルプロジェクトに取得します」— pulls remote changes into the local project, overwriting local files

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

clasp_pull Rate-limited

clasp_pull 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_pull": {
      "limits": [
        {
          "counter": "clasp_pull_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_pull

What does the clasp_pull tool do? +

リモートの変更をローカルプロジェクトに取得します（環境切替対応）. 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_pull? +

Register the Google Apps Script MCP Server MCP server in PolicyLayer and add a rule for clasp_pull: 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_pull? +

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

Can I rate-limit clasp_pull? +

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

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

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