Get list of available nozzle sizes for a printer (or all printers).
AI agents call get_available_nozzles 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.
This tool retrieves and lists nozzle size options from the QIDI Studio configuration. It performs a read-only query with no capability to modify, delete, or execute operations. The blast radius of misuse is minimal—an AI could only retrieve information already present in the local configuration. No data is created, modified, deleted, or executed.
From the tool's definition Tool name 'get_available_nozzles' and description 'Get list of available nozzle sizes for a printer' indicate a retrieval operation that queries configuration data without modification or side effects.
Attacks that exploit this kind of access
Get list of available nozzle sizes for a printer (or all printers). 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 get_available_nozzles: 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.
get_available_nozzles 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_available_nozzles 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_available_nozzles. 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_available_nozzles 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 →