AI agents use modify_doc_text_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.
The tool modifies document content, which is a reversible write operation. While the description is empty (lowering confidence slightly), the name and server context clearly indicate it edits Google Docs text. This is categorized as Write rather than Execute because it directly modifies data rather than executing arbitrary code.
From the tool's definition Tool name 'modify_doc_text_tool' indicates modification of document text. Context shows this is part of an Apps Script MCP server that 'manage[s]...Google Apps Script projects' with sibling tools like 'append_doc_text_tool' and 'create_doc_tool' that create…
Documented attack patterns abuse exactly the kind of access modify_doc_text_tool gives an agent:
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 modify_doc_text_tool:
{
"version": "1",
"default": "deny",
"tools": {
"modify_doc_text_tool": {
"limits": [
{
"counter": "modify_doc_text_tool_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} modify_doc_text_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.
Free to start. No card required.
modify_doc_text_tool. 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.
Register the Apps Script MCP server in PolicyLayer and add a rule for modify_doc_text_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.
modify_doc_text_tool 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_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.
Set action: deny in the PolicyLayer policy for modify_doc_text_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.
modify_doc_text_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.
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.