Get the file system path for a preset.
AI agents call get_preset_path 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 and returns information (a file path) about an existing preset. It has no side effects, does not execute code or shell commands, does not modify data, and does not perform destructive operations. It is a straightforward read operation, consistent with the server's role in managing QIDI Studio 3D printing profiles.
From the tool's definition Tool name 'get_preset_path' and description 'Get the file system path for a preset' indicate a retrieval operation that returns a path without modifying, executing, or deleting data.
Attacks that exploit this kind of access
Get the file system path for a preset. 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_preset_path: 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_preset_path 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_preset_path 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_preset_path. 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_preset_path 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 →