Share a Google Doc with specific users
AI agents use google_docs_share to create or update resources in Google Docs MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Docs MCP Server environment.
Sharing a document grants access permissions to external users, which is a write/modify operation on access control. This is reversible (permissions can be revoked), so it falls under Write rather than Destructive. However, it carries high severity because misuse could expose sensitive documents to unauthorized parties, potentially leaking confidential information.
From the tool's definition Share a Google Doc with specific users
Attacks that exploit this kind of access
Share a Google Doc with specific users. It is categorised as a Write tool in the Google Docs MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Docs MCP Server MCP server in PolicyLayer and add a rule for google_docs_share: 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 Google Docs MCP Server. Nothing to install.
google_docs_share 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 google_docs_share 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 google_docs_share. 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.
google_docs_share is provided by the Google Docs MCP Server MCP server (meerkats-ai/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 →