create_google_doc_from_file
AI agents use create_google_doc_from_file to create or update resources in DCI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DCI MCP Server environment.
The tool creates new documents in Google Drive, a write operation that modifies the user's document store reversibly. While no side effects are irreversible, the action is not a read-only query. Severity is medium because document creation has bounded impact within Google Drive (not financial, not system-critical execution, not destructive).
From the tool's definition Tool name 'create_google_doc_from_file' indicates it creates a Google Doc; context shows server integrates with Google Drive and includes sibling tools like 'create_google_doc_from_markdown' and 'convert_dci_report_to_google_doc' which are write operations.
Attacks that exploit this kind of access
create_google_doc_from_file. It is categorised as a Write tool in the DCI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DCI MCP Server MCP server in PolicyLayer and add a rule for create_google_doc_from_file: 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 DCI MCP Server. Nothing to install.
create_google_doc_from_file 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_google_doc_from_file 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_google_doc_from_file. 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_google_doc_from_file is provided by the DCI MCP Server MCP server (redhat-community-ai-tools/dci-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 →