update_google_doc

Append new content to an existing Google Doc. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]

SERVERFreedom Mcp SOURCEhttps://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp

Medium RISK CLASS

Category Write

Parameters 33 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getfreedomos-freedom-mcp/update-google-doc.md

WHAT IT DOES

What update_google_doc does on Freedom Mcp

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

Parameter	Type	Required	Description
`doc_id`	string	Yes	Google Doc ID to update
`content`	string	Yes	Content to append to the document
`companyId`	string	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.

Parameters from the server's own tool schema.

RISK

Why update_google_doc is rated Medium

This tool creates or modifies document content reversibly (append operation), fitting the Write definition. It does not execute arbitrary code, delete data, move financial resources, or query data. The requirement for manager approval on first use reflects organizational awareness of data modification risks.

From the tool's definition Tool description explicitly states it 'Append[s] new content to an existing Google Doc.' Appending is a reversible modification operation. The tool is further characterized as 'write-tier' in the approval framework, confirming the Write category.

Risk signalsAccepts raw HTML/template content (content)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_google_doc safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_google_doc, this is the rule to start with:

update_google_doc Rate-limited

update_google_doc 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": {
    "update_google_doc": {
      "limits": [
        {
          "counter": "update_google_doc_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every update_google_doc call is checked against it from then on.

FAQ

Questions about update_google_doc

What does the update_google_doc tool do? +

Append new content to an existing Google Doc. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]. It is categorised as a Write tool in the Freedom Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_google_doc accept? +

update_google_doc accepts 3 parameters: doc_id, content, companyId. Required: doc_id, content, companyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_google_doc? +

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

What risk level is update_google_doc? +

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

Can I rate-limit update_google_doc? +

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

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

update_google_doc is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Freedom, and thousands of servers like it.

This server

All 238 Freedom tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →