Invite a user to a document via email
AI agents use docs_invite_user to create or update resources in Docs MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docs MCP Server environment.
Inviting a user grants access to a document by sending an email and modifying access control state. This is reversible (invitations can be cancelled, as evidenced by the sibling tool docs_cancel_invitation), so it falls under Write rather than Destructive. Misuse could expose sensitive documents to unintended parties, warranting medium severity.
From the tool's definition Invite a user to a document via email
Attacks that exploit this kind of access
Invite a user to a document via email. It is categorised as a Write tool in the Docs MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Docs MCP Server MCP server in PolicyLayer and add a rule for docs_invite_user: 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 Docs MCP Server. Nothing to install.
docs_invite_user 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 docs_invite_user 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 docs_invite_user. 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.
docs_invite_user is provided by the Docs MCP Server MCP server (nic01asfr/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 →