AI agents call export_presentation to retrieve information from Gg without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Exporting a presentation retrieves and converts existing data into a different format. It does not modify, delete, or create new data — it is a read/fetch operation. The export formats (pdf, pptx, txt) confirm this is a data retrieval action with no side effects.
From the tool's definition Export a presentation. Formats: pdf, pptx, txt.
Attacks that exploit this kind of access
Export a presentation. Formats: pdf, pptx, txt. It is categorised as a Read tool in the Gg MCP Server, which means it retrieves data without modifying state.
Register the Gg MCP server in PolicyLayer and add a rule for export_presentation: 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 Gg. Nothing to install.
export_presentation 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 export_presentation 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 export_presentation. 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.
export_presentation is provided by the Gg MCP server (tannht/google-cloud-mcp). 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 →