Returns whether a slideshow is currently playing and the current slide number.
AI agents call get_slideshow_status to retrieve information from Keynote MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves presentation state information (slideshow status and current slide number) without modifying, executing, or deleting any data. It is a straightforward query operation that poses minimal security risk even if misused by an agent.
From the tool's definition Tool name 'get_slideshow_status' and description 'Returns whether a slideshow is currently playing and the current slide number' indicate a read-only query operation with no side effects.
Attacks that exploit this kind of access
Returns whether a slideshow is currently playing and the current slide number. It is categorised as a Read tool in the Keynote MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Keynote MCP Server MCP server in PolicyLayer and add a rule for get_slideshow_status: 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 Keynote MCP Server. Nothing to install.
get_slideshow_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_slideshow_status 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 get_slideshow_status. 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.
get_slideshow_status is provided by the Keynote MCP Server MCP server (superdwayne/keynotemp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →