Create document with title, heading, and formatted body text
AI agents use create_formatted_document 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.
This tool creates a new document in Google Docs with structured content (title, heading, body text). Creation is a reversible write operation — the document can be edited or deleted afterward. It does not execute code, delete data irreversibly, or move money.
From the tool's definition Tool description states 'Create document with title, heading, and formatted body text' — the verb 'Create' indicates creation of new data in Google Docs.
Attacks that exploit this kind of access
Create document with title, heading, and formatted body text. 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 create_formatted_document: 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.
create_formatted_document 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 create_formatted_document 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 create_formatted_document. 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.
create_formatted_document 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 →