Returns a ready-to-paste Kotlin (Jetpack Compose) or Swift (SwiftUI) helper that streams an AR session to Rerun. Pick which data types to log — camera pose, detected planes, point clouds, anchors, hit results — and the optional throttle (default 10 Hz). The generated code uses the RerunBridge hel...
Risk signalsAccepts URL/endpoint input (host)
Part of the SceneView 3D & AR server.
Free to start. No card required.
AI agents use generate_ar_logger to create or modify resources in SceneView 3D & AR. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call generate_ar_logger repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach SceneView 3D & AR.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"generate_ar_logger": {
"limits": [
{
"counter": "generate_ar_logger_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full SceneView 3D & AR policy for all 63 tools.
These attack patterns abuse exactly the kind of access generate_ar_logger gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Returns a ready-to-paste Kotlin (Jetpack Compose) or Swift (SwiftUI) helper that streams an AR session to Rerun. Pick which data types to log — camera pose, detected planes, point clouds, anchors, hit results — and the optional throttle (default 10 Hz). The generated code uses the RerunBridge helper (arsceneview.rerun.RerunBridge on Android, SceneViewSwift.RerunBridge on iOS) and drops frames on backpressure so the main thread is never blocked.. It is categorised as a Write tool in the SceneView 3D & AR MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SceneView 3D & AR MCP server in PolicyLayer and add a rule for generate_ar_logger: 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.
generate_ar_logger 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 generate_ar_logger 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 generate_ar_logger. 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.
generate_ar_logger 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.