List all access permissions for a document
AI agents call docs_list_accesses 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 access control information for a document without modifying, executing, or deleting anything. It is purely informational, making it a Read operation. The severity is low because exposure of this capability to an AI agent poses minimal risk—listing permissions is unlikely to cause harm even if misused, though it could inform reconnaissance of document access policies.
From the tool's definition Tool name 'docs_list_accesses' and description 'List all access permissions for a document' indicate a query/retrieval operation with no side effects. The verb 'list' is characteristic of Read category tools.
Attacks that exploit this kind of access
List all access permissions 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_accesses: 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_accesses 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_accesses 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_accesses. 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_accesses 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 →