Get the current AMS filament tray mapping — shows which filament
AI agents call ams_filament_mapping to retrieve information from Bambu Lab MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the current state of the AMS (Automated Material System) filament mapping to display which filament is loaded in each tray. The use of 'Get' and 'shows' confirms it is a read-only operation that retrieves data without creating, modifying, deleting, or executing code. There is no risk of unintended data loss, financial impact, or system damage from misuse.
From the tool's definition Tool name 'ams_filament_mapping' and description 'Get the current AMS filament tray mapping — shows which filament' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access ams_filament_mapping gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bambu Lab MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ams_filament_mapping:
{
"version": "1",
"default": "deny",
"tools": {
"ams_filament_mapping": {}
}
} ams_filament_mapping is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current AMS filament tray mapping — shows which filament. It is categorised as a Read tool in the Bambu Lab MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bambu Lab MCP Server MCP server in PolicyLayer and add a rule for ams_filament_mapping: 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 Lab MCP Server. Nothing to install.
ams_filament_mapping 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 ams_filament_mapping 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 ams_filament_mapping. 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.
ams_filament_mapping is provided by the Bambu Lab MCP Server MCP server (schwarztim/bambu-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bambu Lab MCP Server, 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.
31 Bambu Lab MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.