keynote_start_slideshow
Start playing a Keynote slideshow from a specific slide.
This record as markdown: /tools/io-github-heznpc-iconnect/keynote-start-slideshow.md
What keynote_start_slideshow does on Iconnect
AI agents invoke keynote_start_slideshow to trigger actions in Iconnect. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why keynote_start_slideshow is rated High
This tool triggers external operations (Keynote slideshow execution) whose visible effects depend on the slide argument provided. This is characteristic of Execute category rather than Read (which would only query presentation data) or Write (which would modify presentation content).
From the tool's definition Tool description states 'Start playing a Keynote slideshow' — initiates execution of presentation software with external visible effects (slideshow playback on screen).
Attacks that exploit this kind of access
The rule that runs keynote_start_slideshow 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_start_slideshow, this is the rule to start with:
keynote_start_slideshow stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_start_slideshow call is checked against it from then on.
Questions about keynote_start_slideshow
Start playing a Keynote slideshow from a specific slide. It is categorised as a Execute tool in the Iconnect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Iconnect MCP server in PolicyLayer and add a rule for keynote_start_slideshow: 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_start_slideshow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the keynote_start_slideshow 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_start_slideshow. 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_start_slideshow 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