list_printer_types
AI agents call list_printer_types 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 or enumerates printer type data with no modification or execution capability. Even in the context of a 3D printer control system, listing available printer types is a passive read operation with minimal risk if misused—it returns static configuration data rather than triggering hardware actions or modifying system state.
From the tool's definition Tool name 'list_printer_types' indicates a query operation that retrieves information about available printer types. The empty description and lack of side-effect indicators suggest this is an informational read-only function.
Attacks that exploit this kind of access
list_printer_types. 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 list_printer_types: 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.
list_printer_types 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 list_printer_types 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 list_printer_types. 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.
list_printer_types 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 →