brick_export_scene

Export the scene as JSON or a summary.

SERVERBrick Builder MCP App SOURCEdend/brick-mcp-app

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dend-brick-mcp-app/brick-export-scene.md

WHAT IT DOES

What brick_export_scene does on Brick Builder MCP App

AI agents call brick_export_scene to retrieve information from Brick Builder MCP App without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why brick_export_scene is rated Low

This tool reads and outputs the current scene data in JSON or summary format. It retrieves existing scene state without modifying, deleting, or executing anything. Exporting/serializing data is a read operation with minimal blast radius.

From the tool's definition Export the scene as JSON or a summary

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs brick_export_scene safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Brick Builder MCP App, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For brick_export_scene, this is the rule to start with:

brick_export_scene Allowed

brick_export_scene is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Brick Builder MCP App, apply this rule, and every brick_export_scene call is checked against it from then on.

FAQ

Questions about brick_export_scene

What does the brick_export_scene tool do? +

Export the scene as JSON or a summary. It is categorised as a Read tool in the Brick Builder MCP App MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on brick_export_scene? +

Register the Brick Builder MCP App MCP server in PolicyLayer and add a rule for brick_export_scene: 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 Brick Builder MCP App. Nothing to install.

What risk level is brick_export_scene? +

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

Can I rate-limit brick_export_scene? +

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

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

brick_export_scene is provided by the Brick Builder MCP App MCP server (dend/brick-mcp-app). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Brick Builder MCP App, and thousands of servers like it.

This server

All 9 Brick Builder MCP App tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →