AI agents use export_scene to create or update resources in SketchupMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SketchupMCP environment.
Export operations create new files or serialized outputs from existing data, making this a Write action rather than a Read (which would merely query data without creating artifacts). It does not irreversibly delete data (not Destructive), execute arbitrary code (not Execute), or involve financial transactions (not Financial).
From the tool's definition The tool 'export_scene' exports the current scene, which creates a new file or output artifact based on existing scene data. This is a data creation/writing operation that produces a persistent artifact (exported file).
Documented attack patterns abuse exactly the kind of access export_scene gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SketchupMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for export_scene:
{
"version": "1",
"default": "deny",
"tools": {
"export_scene": {
"limits": [
{
"counter": "export_scene_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_scene 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.
Export the current scene. It is categorised as a Write tool in the SketchupMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sketchup MCP server in PolicyLayer and add a rule for 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 SketchupMCP. Nothing to install.
export_scene 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 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.
Set action: deny in the PolicyLayer policy for 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.
export_scene is provided by the Sketchup MCP server (mhyrr/sketchup-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SketchupMCP, 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.
10 SketchupMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.