Designs multiple slides at once with automatic layout variety and consistent branding
AI agents use design_deck to create or update resources in Keynote MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Keynote MCP Server environment.
design_deck creates and modifies presentation slides programmatically, which are reversible changes to the presentation document. It does not delete data (Destructive), move money (Financial), or execute arbitrary code (Execute)—it operates within a bounded domain of presentation design operations.
From the tool's definition Tool description states it 'Designs multiple slides at once' and performs automatic layout and branding operations on a presentation.
Attacks that exploit this kind of access
Designs multiple slides at once with automatic layout variety and consistent branding. It is categorised as a Write tool in the Keynote MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Keynote MCP Server MCP server in PolicyLayer and add a rule for design_deck: 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.
design_deck 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 design_deck 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 design_deck. 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.
design_deck 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 →