script_add_function · Gworkspace MCP: Risk & Policy

WHAT IT DOES

What script_add_function does on Gworkspace

AI agents use script_add_function 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_add_function needs a policy

This tool modifies code by adding functions to existing files, which is a reversible Write operation. While it could potentially introduce malicious code if misused by an AI agent (especially given Apps Script's capability to access Google Workspace data and trigger external operations), the tool itself is fundamentally a Write operation—it appends content rather than executing it.

From the tool's definition Tool description states 'Add a new function to an existing file. Appends at the end.' - this is a modification operation that creates new code within an existing Apps Script file.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

script_add_function Rate-limited

script_add_function 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_add_function": {
      "limits": [
        {
          "counter": "script_add_function_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_add_function

What does the script_add_function tool do? +

Add a new function to an existing file. Appends at the end. 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_add_function? +

Register the Gworkspace MCP server in PolicyLayer and add a rule for script_add_function: 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_add_function? +

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

Can I rate-limit script_add_function? +

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

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

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