google_docs_get_permissions
Get sharing permissions for a Google Doc
This record as markdown: /tools/sagemcp-sagemcp/google-docs-get-permissions.md
What google_docs_get_permissions does on Sage MCP
AI agents call google_docs_get_permissions to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why google_docs_get_permissions is rated Low
This tool queries and retrieves sharing permission information from a Google Doc. It performs a read-only operation that does not create, modify, delete, or execute any actions. The blast radius is minimal—exposure would allow an agent to see who has access to a document, but not to grant, revoke, or modify permissions, nor to access the document content itself. This is a standard information retrieval operation.
From the tool's definition Tool name 'google_docs_get_permissions' and description 'Get sharing permissions for a Google Doc' indicate retrieval of existing permission metadata without modification or side effects.
Attacks that exploit this kind of access
The rule that runs google_docs_get_permissions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google_docs_get_permissions, this is the rule to start with:
google_docs_get_permissions 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 Sage MCP, apply this rule, and every google_docs_get_permissions call is checked against it from then on.
Questions about google_docs_get_permissions
Get sharing permissions for a Google Doc. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for google_docs_get_permissions: 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 Sage MCP. Nothing to install.
google_docs_get_permissions 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 google_docs_get_permissions 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_get_permissions. 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_get_permissions is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sage, and thousands of servers like it.
This server
Across the catalogue