High Risk →

animate_camera_presets

Animate the camera through a sequence of saved presets

How to control animate_camera_presets ↓

What animate_camera_presets does on Threlte

AI agents invoke animate_camera_presets to trigger actions in Threlte. 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.

High Risk

Why animate_camera_presets needs a policy

This tool executes a camera animation sequence in a Three.js/Threlte scene. It triggers external operations (animating the camera) whose effects depend on the provided preset arguments. It's not purely reading data, nor is it destructive or financial — it drives runtime behavior in a live scene, placing it in the Execute category.

From the tool's definition 'Animate the camera through a sequence of saved presets' — triggers real-time animation/movement operations in a live 3D scene

Documented attack patterns abuse exactly the kind of access animate_camera_presets gives an agent:

How to control animate_camera_presets

PolicyLayer is an MCP gateway — it sits between your AI agents and Threlte, and nothing reaches the server without passing your rules. This is the rule we recommend for animate_camera_presets:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "animate_camera_presets": {
      "limits": [
        {
          "counter": "animate_camera_presets_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

animate_camera_presets stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Threlte — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about animate_camera_presets

What does the animate_camera_presets tool do? +

Animate the camera through a sequence of saved presets. It is categorised as a Execute tool in the Threlte MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on animate_camera_presets? +

Register the Threlte MCP server in PolicyLayer and add a rule for animate_camera_presets: 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 Threlte. Nothing to install.

What risk level is animate_camera_presets? +

animate_camera_presets is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit animate_camera_presets? +

Yes. Add a rate_limit block to the animate_camera_presets 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.

How do I block animate_camera_presets completely? +

Set action: deny in the PolicyLayer policy for animate_camera_presets. 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.

What MCP server provides animate_camera_presets? +

animate_camera_presets is provided by the Threlte MCP server (serifeusstudio/threlte-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Threlte tool call.

Start from Threlte, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

30 Threlte tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.