keynote_close_document
Close an open Keynote presentation, optionally saving changes.
This record as markdown: /tools/heznpc-airmcp/keynote-close-document.md
What keynote_close_document does on AirMCP
AI agents use keynote_close_document to create or update resources in AirMCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AirMCP environment.
Why keynote_close_document is rated Medium
This tool modifies state by closing a presentation and potentially persisting unsaved changes to disk. While the changes themselves were made elsewhere, this tool is the mechanism that commits them. The impact is reversible (user can reopen and edit again), so it is Write rather than Destructive.
From the tool's definition Tool description states 'Close an open Keynote presentation, optionally saving changes.' The 'optionally saving changes' clause indicates the tool can persist modifications to a document, making it a write operation.
Attacks that exploit this kind of access
The rule that runs keynote_close_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For keynote_close_document, this is the rule to start with:
keynote_close_document 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.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every keynote_close_document call is checked against it from then on.
Questions about keynote_close_document
Close an open Keynote presentation, optionally saving changes. It is categorised as a Write tool in the AirMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Air MCP server in PolicyLayer and add a rule for keynote_close_document: 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 AirMCP. Nothing to install.
keynote_close_document 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 keynote_close_document 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 keynote_close_document. 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.
keynote_close_document is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue