Update a single setting key in a profile. By default (dry_run=true), the change is saved to a _tuned copy rather than overwriting the original.
AI agents use update_profile_setting to create or update resources in OrcaSlicer MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OrcaSlicer MCP Server environment.
This tool modifies printer profile settings, which are reversible changes (the original is preserved by default with dry_run=true). It does not execute print jobs, delete data, or cause physical irreversible effects.
From the tool's definition Tool description states it 'Update[s] a single setting key in a profile' and 'change is saved to a _tuned copy rather than overwriting the original', indicating reversible modification of configuration data.
Attacks that exploit this kind of access
Update a single setting key in a profile. By default (dry_run=true), the change is saved to a _tuned copy rather than overwriting the original. It is categorised as a Write tool in the OrcaSlicer MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OrcaSlicer MCP Server MCP server in PolicyLayer and add a rule for update_profile_setting: 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 OrcaSlicer MCP Server. Nothing to install.
update_profile_setting is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_profile_setting 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 update_profile_setting. 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.
update_profile_setting is provided by the OrcaSlicer MCP Server MCP server (itsumonotakumi/orcaslicer-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 →