Insert text at a specific position in the document
AI agents use insert_text to create or update resources in LLM2Docs (Unofficial) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LLM2Docs (Unofficial) environment.
The tool creates or modifies document content by inserting text at a specified location. This is a reversible write operation — the inserted text can be deleted or edited. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), involves no financial impact (not Financial), and is not a read-only retrieval (not Read). Write category applies.
From the tool's definition Tool name is 'insert_text' and description states it 'Insert[s] text at a specific position in the document'. This is a data modification operation.
Attacks that exploit this kind of access
Insert text at a specific position in the document. It is categorised as a Write tool in the LLM2Docs (Unofficial) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LLM2Docs (Unofficial) MCP server in PolicyLayer and add a rule for insert_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 LLM2Docs (Unofficial). Nothing to install.
insert_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 insert_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 insert_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.
insert_text is provided by the LLM2Docs (Unofficial) MCP server (nomannayeem/google-docs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →