Insert a table into the document
AI agents use insert_table 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.
Inserting a table modifies the document by adding new content, making it a Write operation rather than Read. It is reversible (tables can be deleted), so it does not qualify as Destructive. The severity is medium because unauthorized insertion of tables could disrupt document formatting and mislead readers, but the impact is limited to a single document and easily correctable.
From the tool's definition Tool description states 'Insert a table into the document', which creates new structured content within a Google Doc. The sibling tools (append_text, apply_font_formatting, apply_heading) confirm this server performs content modification operations.
Attacks that exploit this kind of access
Insert a table into 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_table: 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_table 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_table 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_table. 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_table 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 →