Get list of detected filament vendors/brands (Generic, QIDI, HATCHBOX, etc.).
AI agents call get_available_vendors 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 queries a list of filament vendors/brands from the QIDI Studio system. It performs no data modification, deletion, or external execution. The operation is informational and has no side effects beyond returning existing enumerated data. This is a straightforward Read operation with minimal security risk.
From the tool's definition Tool name 'get_available_vendors' and description 'Get list of detected filament vendors/brands' indicate a read-only operation that retrieves and lists predefined vendor data without modification or side effects.
Attacks that exploit this kind of access
Get list of detected filament vendors/brands (Generic, QIDI, HATCHBOX, etc.). 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_vendors: 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_vendors 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_vendors 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_vendors. 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_vendors 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 →