Update the speaker notes for a specific slide
AI agents use google_slides_update_speaker_notes to create or update resources in Sage MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sage MCP environment.
This tool modifies speaker notes on a Google Slides presentation, which is reversible data modification. It does not execute code, delete data, move money, or trigger external operations with unpredictable effects. The blast radius is limited to speaker notes content, which typically does not affect live presentations or critical workflows.
From the tool's definition Tool name contains 'update' and description states 'Update the speaker notes for a specific slide', indicating modification of existing data.
Documented attack patterns abuse exactly the kind of access google_slides_update_speaker_notes 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_slides_update_speaker_notes:
{
"version": "1",
"default": "deny",
"tools": {
"google_slides_update_speaker_notes": {
"limits": [
{
"counter": "google_slides_update_speaker_notes_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}google_slides_update_speaker_notes stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update the speaker notes for a specific slide. It is categorised as a Write tool in the Sage MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sage MCP server in PolicyLayer and add a rule for google_slides_update_speaker_notes: 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_slides_update_speaker_notes is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the google_slides_update_speaker_notes 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_slides_update_speaker_notes. 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_slides_update_speaker_notes 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.