keynote_close_document

Close an open Keynote presentation, optionally saving changes.

SERVERIconnect SOURCEiconnect-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about keynote_close_document

What does the keynote_close_document tool do? +

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.

How do I enforce a policy on keynote_close_document? +

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.

What risk level is keynote_close_document? +

keynote_close_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit keynote_close_document? +

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.

How do I block keynote_close_document completely? +

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.

What MCP server provides keynote_close_document? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Iconnect's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.