Run print validation. Returns errors and warnings that would block or affect printing.
AI agents call get_print_validation 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.
The tool runs a validation check and returns errors/warnings. It reads and analyzes the print configuration but does not modify data, trigger printing, or cause any side effects. Severity is medium because misuse or misinterpretation of validation results could indirectly affect 3D printing operations.
From the tool's definition 'Run print validation. Returns errors and warnings that would block or affect printing.'
Attacks that exploit this kind of access
Run print validation. Returns errors and warnings that would block or affect printing. 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_print_validation: 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_print_validation 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_print_validation 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_print_validation. 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_print_validation 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 →