Get the full state of a scene including loaded models and print settings.
AI agents call get_scene to retrieve information from Formlabs Local without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the current state of a scene (models and print settings) without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal risk even if called repeatedly or with unexpected parameters. The worst-case scenario is information disclosure about the current printer state, which is low severity in the context of printer automation.
From the tool's definition Tool description states 'Get the full state' which indicates retrieval of data without modification. The verb 'get' is explicitly listed as a Read-category operation in the guidelines.
Attacks that exploit this kind of access
Get the full state of a scene including loaded models and print settings. It is categorised as a Read tool in the Formlabs Local MCP Server, which means it retrieves data without modifying state.
Register the Formlabs Local MCP server in PolicyLayer and add a rule for get_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 Formlabs Local. Nothing to install.
get_scene 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 get_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 get_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.
get_scene is provided by the Formlabs Local MCP server (mkebiclioglu/formlabs-local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →