3D光照动画
AI agents invoke lighting_3d_animation to trigger actions in GSAP MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on the server context, this tool generates GSAP animation code, which constitutes executing or triggering code/scripts. The description is minimal ('3D lighting animation' in Chinese), so confidence is moderate. Within this server's pattern of animation code generation and execution tools, this tool likely generates and runs 3D lighting animation code, placing it in the Execute category.
From the tool's definition Tool name 'lighting_3d_animation' and description '3D光照动画' (3D lighting animation) — generates and executes GSAP animation code for 3D lighting effects
Attacks that exploit this kind of access
3D光照动画. It is categorised as a Execute tool in the GSAP MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GSAP MCP Server MCP server in PolicyLayer and add a rule for lighting_3d_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.
lighting_3d_animation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the lighting_3d_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 lighting_3d_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.
lighting_3d_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 →