动画调试工具
AI agents use debug_animation to create or update resources in GSAP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GSAP MCP Server environment.
An AI agent can call debug_animation faster than any human can review — one bad instruction and it creates or modifies resources in GSAP MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
动画调试工具. It is categorised as a Write tool in the GSAP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GSAP MCP Server MCP server in PolicyLayer and add a rule for debug_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 GSAP MCP Server. Nothing to install.
debug_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 debug_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 debug_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.
debug_animation is provided by the GSAP MCP Server MCP server (lillard01/gsap-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 →