list_profiles
AI agents call list_profiles to retrieve information from QIDI Studio MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool's name 'list_profiles' clearly indicates it retrieves or enumerates 3D printing profiles without modifying them. This aligns with the Read category (search, list, get, fetch). Even though no description was provided, the semantic meaning of 'list' is unambiguous. Confidence is slightly reduced due to lack of descriptive detail, but the name provides sufficient evidence.
From the tool's definition Tool name 'list_profiles' indicates a retrieval/query operation typical of Read category. The verb 'list' is explicitly listed in Read examples. No description provided, but the name strongly suggests data retrieval without modification.
Attacks that exploit this kind of access
list_profiles. It is categorised as a Read tool in the QIDI Studio MCP Server MCP Server, which means it retrieves data without modifying state.
Register the QIDI Studio 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 QIDI Studio 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 QIDI Studio MCP Server MCP server (vladyankovenko/qidi-studio-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 →