list_camera_presets

THE RISK

Low Risk

Why list_camera_presets needs a policy

This tool queries and returns information about existing camera presets without modifying, deleting, or executing any operations. It is a straightforward read operation with minimal risk if misused by an AI agent.

From the tool's definition Tool name 'list_camera_presets' and description 'List all available camera presets' indicate a retrieval operation with no side effects.

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

POLICY

How to control list_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 list_camera_presets:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_camera_presets": {}
  }
}

list_camera_presets is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Threlte — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Threlte tools

Destructive delete_camera_preset Delete a saved camera preset Destructive destroy_entity Remove an entity from the scene Execute animate_camera_presets Animate the camera through a sequence of saved presets Execute apply_impulse Apply an impulse force to a physics object Write remove_physics Remove physics body from an object Write load_asset Load a GLTF/GLB model into the scene Write load_camera_preset Load a saved camera preset and optionally animate to it Write apply_material Apply a material to an object

All 30 Threlte tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_camera_presets

What does the list_camera_presets tool do? +

List all available camera presets. It is categorised as a Read tool in the Threlte MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_camera_presets? +

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

list_camera_presets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_camera_presets? +

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

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

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

CHECK YOUR STACK →