AI agents call google_docs_get_permissions to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access google_docs_get_permissions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for google_docs_get_permissions:
{
"version": "1",
"default": "deny",
"tools": {
"google_docs_get_permissions": {}
}
}google_docs_get_permissions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.