Modify text in a Google Doc - insert/replace text and/or apply formatting
AI agents use modify_doc_text to create or update resources in VaultAssist — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VaultAssist environment.
This tool modifies document content reversibly through text insertion, replacement, and formatting changes. These are Write operations (create/modify data). Severity is medium because misuse could corrupt important documents, but changes are typically reversible through Google Docs version history. The tool operates within OAuth 2.1 secured Google Workspace with vault-level security limiting the blast radius.
From the tool's definition Tool description states 'Modify text in a Google Doc - insert/replace text and/or apply formatting', which are create/modify operations on document content.
Documented attack patterns abuse exactly the kind of access modify_doc_text gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VaultAssist, and nothing reaches the server without passing your rules. This is the rule we recommend for modify_doc_text:
{
"version": "1",
"default": "deny",
"tools": {
"modify_doc_text": {
"limits": [
{
"counter": "modify_doc_text_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}modify_doc_text 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.
Free to start. No card required.
Modify text in a Google Doc - insert/replace text and/or apply formatting. It is categorised as a Write tool in the VaultAssist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VaultAssist MCP server in PolicyLayer and add a rule for modify_doc_text: 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 VaultAssist. Nothing to install.
modify_doc_text is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the modify_doc_text 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.
Set action: deny in the PolicyLayer policy for modify_doc_text. 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.
modify_doc_text is provided by the VaultAssist MCP server (3xcaffeine/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VaultAssist, 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.
79 VaultAssist tools catalogued and risk-classified — across an index of 43,000+ MCP servers.