Validates a Kotlin SceneView snippet for common interior-design app mistakes. Checks threading violations (Filament JNI on background thread), null-safety for model loading, LightNode trailing-lambda bug, deprecated 2.x APIs, unsupported format warnings (FBX, OBJ, 3DS), texture size warnings, and...
Risk signalsAccepts freeform code/query input (code)
Part of the SceneView 3D & AR server.
Free to start. No card required.
AI agents call validate_interior_code to retrieve information from SceneView 3D & AR without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though validate_interior_code only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"validate_interior_code": {}
}
}See the full SceneView 3D & AR policy for all 63 tools.
These attack patterns abuse exactly the kind of access validate_interior_code gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Validates a Kotlin SceneView snippet for common interior-design app mistakes. Checks threading violations (Filament JNI on background thread), null-safety for model loading, LightNode trailing-lambda bug, deprecated 2.x APIs, unsupported format warnings (FBX, OBJ, 3DS), texture size warnings, and multiple model instance performance. Always call this before presenting generated interior SceneView code.. It is categorised as a Read tool in the SceneView 3D & AR MCP Server, which means it retrieves data without modifying state.
Register the SceneView 3D & AR MCP server in PolicyLayer and add a rule for validate_interior_code: 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 SceneView 3D & AR. Nothing to install.
validate_interior_code is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the validate_interior_code 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 validate_interior_code. 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.
validate_interior_code is provided by the SceneView 3D & AR MCP server (sceneview/gateway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 63 SceneView 3D & AR tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.