AI agents call get_user_profile 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 performs a read-only operation that retrieves user account information. It does not modify, delete, or execute any actions. The blast radius is minimal—exposure of this tool could reveal user profile details but cannot cause damage to printer operations, financial harm, or destructive actions. Low severity reflects the informational nature of the retrieval.
From the tool's definition The tool description explicitly states 'Get Bambu Lab cloud account profile', which is a retrieval operation with no side effects. It queries user profile data from the Bambu Lab cloud service.
Documented attack patterns abuse exactly the kind of access get_user_profile 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 get_user_profile:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_profile": {}
}
} get_user_profile 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 Bambu Lab cloud account profile. 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 get_user_profile: 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.
get_user_profile 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_user_profile 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_user_profile. 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_user_profile 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.