clasp_push_and_deploy · Google Apps Script MCP Server MCP

WHAT IT DOES

What clasp_push_and_deploy does on Google Apps Script MCP Server

AI agents invoke clasp_push_and_deploy to trigger actions in Google Apps Script MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why clasp_push_and_deploy needs a policy

This tool pushes local code changes to Google Apps Script and optionally deploys them as a web app or other GAS deployment. Pushing and deploying code is an Execute-category action: it uploads files and triggers external service operations (deployment).

From the tool's definition 'プッシュし' (push) and 'デプロイします' (deploy) — pushes local changes and deploys them, triggering external operations on Google Apps Script

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

clasp_push_and_deploy Rate-limited

clasp_push_and_deploy stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_push_and_deploy": {
      "limits": [
        {
          "counter": "clasp_push_and_deploy_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_push_and_deploy

What does the clasp_push_and_deploy tool do? +

ローカルの変更をプッシュし、必要に応じてデプロイします（環境切替対応）. It is categorised as a Execute tool in the Google Apps Script MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on clasp_push_and_deploy? +

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

clasp_push_and_deploy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit clasp_push_and_deploy? +

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

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

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