List available profile files for a given category (machine, filament, or process).
AI agents call list_profiles to retrieve information from OrcaSlicer 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 simple enumeration of existing profiles in specified categories (machine, filament, process). It retrieves information only and does not create, modify, delete, or execute operations. It poses minimal risk if misused by an AI agent, as the worst outcome would be information disclosure of available profiles.
From the tool's definition Tool name 'list_profiles' and description 'List available profile files for a given category' indicate a retrieval operation with no side effects—it queries and returns data without modifying or executing anything.
Attacks that exploit this kind of access
List available profile files for a given category (machine, filament, or process). It is categorised as a Read tool in the OrcaSlicer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OrcaSlicer MCP Server MCP server in PolicyLayer and add a rule for list_profiles: 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.
list_profiles 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_profiles 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_profiles. 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_profiles 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 →