Get the QIDI Studio configuration directory path.
AI agents call get_config_directory 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 performs a simple query operation to retrieve the configuration directory path. It does not modify, execute, or delete any data. The operation is read-only and poses minimal risk even if misused by an agent, as it only exposes a directory path that is typically discoverable through standard system utilities. No reversible writes, irreversible deletions, code execution, or financial operations are involved.
From the tool's definition Tool name 'get_config_directory' and description 'Get the QIDI Studio configuration directory path' indicate a retrieval operation that returns a filesystem path with no side effects.
Attacks that exploit this kind of access
Get the QIDI Studio configuration directory path. 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_config_directory: 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_config_directory 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_config_directory 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_config_directory. 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_config_directory 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 →