AI agents call keynote_get_slide to retrieve information from Keynote without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns data about slide structure, elements, fonts, colors, and positions. It does not create, modify, delete, or execute any operations. No data is changed, no code is run, and no side effects occur. The verb 'get' and the stated purpose of understanding structure before editing confirm this is a pure read operation.
From the tool's definition Tool retrieves 'full element tree for a single slide' with structural and styling information. Description explicitly states 'Use this to understand the structure of a slide before editing it' - a read/query operation with no side effects.
Attacks that exploit this kind of access
Get the full element tree for a single slide: all text boxes, images, and shapes with their position, size, font, and color. Use this to understand the structure of a slide before editing it. It is categorised as a Read tool in the Keynote MCP Server, which means it retrieves data without modifying state.
Register the Keynote MCP server in PolicyLayer and add a rule for keynote_get_slide: 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. Nothing to install.
keynote_get_slide 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 keynote_get_slide 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_get_slide. 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_get_slide is provided by the Keynote MCP server (tszaks/keynote-mcp). 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 →