Inspect slicer settings from a saved 3MF template or a JSON/config slicer profile without slicing anything.
AI agents call get_slice_settings to retrieve information from Bambu Printer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves slicer configuration settings without modifying files, executing operations, or triggering any printer actions. It is purely informational and poses minimal risk.
From the tool's definition Tool description states 'Inspect slicer settings from a saved 3MF template or a JSON/config slicer profile without slicing anything.' The word 'Inspect' and explicit statement of non-execution ('without slicing anything') indicate read-only retrieval of…
Attacks that exploit this kind of access
Inspect slicer settings from a saved 3MF template or a JSON/config slicer profile without slicing anything. It is categorised as a Read tool in the Bambu Printer MCP Server, which means it retrieves data without modifying state.
Register the Bambu Printer MCP server in PolicyLayer and add a rule for get_slice_settings: 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 Bambu Printer. Nothing to install.
get_slice_settings 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_slice_settings 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_slice_settings. 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_slice_settings is provided by the Bambu Printer MCP server (rowbotik/bambu-printer-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 →