Medium Risk

update_deployment_tool

Update an existing deployment configuration.

How to control update_deployment_tool ↓

What update_deployment_tool does on Apps Script MCP

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

Medium Risk

Why update_deployment_tool needs a policy

This tool modifies an existing deployment's configuration, which is a reversible write operation. While deployment changes can have significant impact on running scripts, the operation itself is typically reversible by updating again. It does not delete, execute arbitrary code, or involve financial transactions.

From the tool's definition Update an existing deployment configuration

Documented attack patterns abuse exactly the kind of access update_deployment_tool gives an agent:

How to control update_deployment_tool

PolicyLayer is an MCP gateway — it sits between your AI agents and Apps Script MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for update_deployment_tool:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_deployment_tool": {
      "limits": [
        {
          "counter": "update_deployment_tool_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Apps Script MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about update_deployment_tool

What does the update_deployment_tool tool do? +

Update an existing deployment configuration. It is categorised as a Write tool in the Apps Script MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_deployment_tool? +

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

What risk level is update_deployment_tool? +

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

Can I rate-limit update_deployment_tool? +

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

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

update_deployment_tool is provided by the Apps Script MCP server (sam-ent/google-automation-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Apps Script MCP tool call.

Start from Apps Script MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

60 Apps Script MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.