Apply batch updates to a Google Slides presentation
AI agents use batch_update_presentation to create or update resources in VaultAssist — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VaultAssist environment.
This tool creates or modifies data reversibly within Google Slides presentations. While updates are not destructive (data is not irreversibly deleted), they do alter existing content. Severity is high because batch operations on presentations could affect large amounts of shared organizational content, and misuse by an AI agent could corrupt or deface important documents accessed by multiple users.
From the tool's definition Tool name 'batch_update_presentation' and description 'Apply batch updates to a Google Slides presentation' indicate the tool modifies existing presentation content.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_update_presentation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VaultAssist, and nothing reaches the server without passing your rules. This is the rule we recommend for batch_update_presentation:
{
"version": "1",
"default": "deny",
"tools": {
"batch_update_presentation": {
"limits": [
{
"counter": "batch_update_presentation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}batch_update_presentation 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.
Apply batch updates to a Google Slides presentation. It is categorised as a Write tool in the VaultAssist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VaultAssist MCP server in PolicyLayer and add a rule for batch_update_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 VaultAssist. Nothing to install.
batch_update_presentation 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 batch_update_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 batch_update_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.
batch_update_presentation is provided by the VaultAssist MCP server (3xcaffeine/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VaultAssist, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
79 VaultAssist tools catalogued and risk-classified — across an index of 43,000+ MCP servers.