Medium Risk

set_camera_position

Set camera position with optional lookAt target and lens settings

How to control set_camera_position ↓

What set_camera_position does on Threlte

AI agents use set_camera_position to create or update resources in Threlte — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Threlte environment.

Medium Risk

Why set_camera_position needs a policy

This tool modifies the camera's position, orientation, and lens settings in a 3D scene. It creates or modifies state reversibly (the camera can be repositioned again), placing it in the Write category. Misuse could disrupt a live scene's viewpoint but is not irreversible or financially impactful.

From the tool's definition Set camera position with optional lookAt target and lens settings

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

How to control set_camera_position

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 set_camera_position:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_camera_position": {
      "limits": [
        {
          "counter": "set_camera_position_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

set_camera_position 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.

  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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about set_camera_position

What does the set_camera_position tool do? +

Set camera position with optional lookAt target and lens settings. It is categorised as a Write tool in the Threlte MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_camera_position? +

Register the Threlte MCP server in PolicyLayer and add a rule for set_camera_position: 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 set_camera_position? +

set_camera_position is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_camera_position? +

Yes. Add a rate_limit block to the set_camera_position 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 set_camera_position completely? +

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

set_camera_position 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.