List all pending invitations for a document
AI agents call docs_list_invitations to retrieve information from Docs MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about pending invitations without creating, modifying, deleting, or executing any actions. It is a straightforward read operation that queries the state of document access invitations. The blast radius is minimal—an AI agent misusing this would only see invitation metadata it likely already has access to.
From the tool's definition Tool name 'docs_list_invitations' and description 'List all pending invitations for a document' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all pending invitations for a document. It is categorised as a Read tool in the Docs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Docs MCP Server MCP server in PolicyLayer and add a rule for docs_list_invitations: 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_list_invitations is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the docs_list_invitations 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_list_invitations. 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_list_invitations 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 →