Add OrbitControls to Three.js scene
AI agents use scene_add_orbit_controls to create or update resources in 8th Wall MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 8th Wall MCP Server environment.
This tool creates or modifies scene state by injecting OrbitControls, which is a reversible write operation. It does not read-only (not a pure query), does not execute arbitrary code (it performs a specific framework operation), and is not destructive, financial, or an external trigger. The modification is within the WebAR scene context and can be undone or replaced.
From the tool's definition Tool name 'scene_add_orbit_controls' and description 'Add OrbitControls to Three.js scene' indicate it modifies/creates a scene configuration by adding interactive orbit controls to an existing Three.js scene.
Documented attack patterns abuse exactly the kind of access scene_add_orbit_controls gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 8th Wall MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for scene_add_orbit_controls:
{
"version": "1",
"default": "deny",
"tools": {
"scene_add_orbit_controls": {
"limits": [
{
"counter": "scene_add_orbit_controls_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}scene_add_orbit_controls 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.
Free to start. No card required.
Add OrbitControls to Three.js scene. It is categorised as a Write tool in the 8th Wall MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 8th Wall MCP Server MCP server in PolicyLayer and add a rule for scene_add_orbit_controls: 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 8th Wall MCP Server. Nothing to install.
scene_add_orbit_controls 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 scene_add_orbit_controls 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 scene_add_orbit_controls. 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.
scene_add_orbit_controls is provided by the 8th Wall MCP Server MCP server (superdwayne/8thwallmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from 8th Wall MCP Server, 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.
64 8th Wall MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.