Copy animation effects from one shape to another on the same slide.
AI agents use ppt_copy_animation to create or update resources in Ppt — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ppt environment.
Copying animation effects creates or modifies presentation elements reversibly. This is a Write operation as it changes slide content without being destructive (animations can be removed or modified). Severity is medium because misuse could degrade presentation quality or create unintended visual effects, but no data is lost and changes are easily undone.
From the tool's definition Tool name 'ppt_copy_animation' and description 'Copy animation effects from one shape to another on the same slide' indicate the tool modifies presentation content by duplicating animation properties between shapes.
Documented attack patterns abuse exactly the kind of access ppt_copy_animation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ppt, and nothing reaches the server without passing your rules. This is the rule we recommend for ppt_copy_animation:
{
"version": "1",
"default": "deny",
"tools": {
"ppt_copy_animation": {
"limits": [
{
"counter": "ppt_copy_animation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ppt_copy_animation stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Copy animation effects from one shape to another on the same slide. It is categorised as a Write tool in the Ppt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ppt MCP server in PolicyLayer and add a rule for ppt_copy_animation: 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 Ppt. Nothing to install.
ppt_copy_animation 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 ppt_copy_animation 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 ppt_copy_animation. 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.
ppt_copy_animation is provided by the Ppt MCP server (ykuwai/ppt-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 156 Ppt tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
156 Ppt tools catalogued and risk-classified — across an index of 42,500+ MCP servers.