script_update_file · Gworkspace MCP: Risk & Policy

WHAT IT DOES

What script_update_file does on Gworkspace

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

WHY IT NEEDS A POLICY

Why script_update_file needs a policy

This tool creates or modifies data reversibly by replacing file contents in a Google Apps Script project. While the operation is reversible (the old content could theoretically be recovered from version history), the high severity reflects the significant blast radius: an AI agent could inadvertently overwrite critical business logic, authentication code, or automation scripts that other systems depend on.

From the tool's definition The tool description states it will 'Replace the entire content of a file in the script project.' This is a write operation that modifies existing file content.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

script_update_file Rate-limited

script_update_file 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": {
    "script_update_file": {
      "limits": [
        {
          "counter": "script_update_file_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 Gworkspace, so you can run agents against it safely.

FAQ

Questions about script_update_file

What does the script_update_file tool do? +

Replace the entire content of a file in the script project. It is categorised as a Write tool in the Gworkspace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on script_update_file? +

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

What risk level is script_update_file? +

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

Can I rate-limit script_update_file? +

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

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

script_update_file is provided by the Gworkspace MCP server (leoonic/gworkspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.