keynote_close_document
Close an open Keynote presentation, optionally saving changes.
This record as markdown: /tools/io-github-heznpc-iconnect/keynote-close-document.md
What keynote_close_document does on Iconnect
AI agents use keynote_close_document to create or update resources in Iconnect, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iconnect environment.
Why keynote_close_document is rated Medium
This tool performs a reversible Write operation by potentially saving changes to a Keynote presentation file. Although closing a presentation without saving is a read-only action, the tool's capability to save changes means it can modify file data. The severity is medium because the impact is limited to a single user's local presentation file, not a system-wide operation or shared resource.
From the tool's definition 'Close an open Keynote presentation, optionally saving changes.' The tool can save changes to a document, which modifies persistent file state. While closing itself is not destructive, the optional save action creates or overwrites document data.
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 Iconnect, 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 Iconnect, 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 Iconnect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iconnect 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 Iconnect. 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 Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue