This record as markdown: /tools/ark7-google-drive-mcp/listpermissions.md
What listPermissions does on Google Drive
AI agents call listPermissions to retrieve information from Google Drive without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
fileId | string | Yes | Google Drive file ID |
account | string | — | Alias of the Google account to target. Optional — defaults to the session/global default account, or the sole authenticated account. Run manage_accounts list to |
Parameters from the server's own tool schema.
Why listPermissions is rated Low
This tool retrieves information about who has access to a file (read-only operation). There are no side effects, data modifications, deletions, or external operations triggered. While permission data could be sensitive, the operation itself is a straightforward informational query with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'listPermissions' and description 'List sharing permissions for a file' indicate a query operation that retrieves metadata about existing permissions without modifying them.
Attacks that exploit this kind of access
The rule that runs listPermissions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For listPermissions, this is the rule to start with:
listPermissions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Drive, apply this rule, and every listPermissions call is checked against it from then on.
Questions about listPermissions
List sharing permissions for a file. It is categorised as a Read tool in the Google Drive MCP Server, which means it retrieves data without modifying state.
listPermissions accepts 2 parameters: fileId, account. Required: fileId. The full parameter table on this page comes from the server's own tool schema.
Register the Google Drive MCP server in PolicyLayer and add a rule for listPermissions: 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 Drive. Nothing to install.
listPermissions 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 listPermissions 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 listPermissions. 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.
listPermissions is provided by the Google Drive MCP server (@ark7/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Drive, and thousands of servers like it.
This server
Across the catalogue