Get information about the currently loaded configuration, including available workflows.
AI agents call get_loaded_config to retrieve information from Qontinui 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 queries existing configuration data without creating, modifying, executing, or deleting anything. It is a pure read operation that returns metadata about currently loaded workflows. The low severity reflects minimal blast radius - an agent can only view configuration details, not alter or execute them.
From the tool's definition Tool description states 'Get information about the currently loaded configuration' - a retrieval operation with no modification or execution of workflows.
Attacks that exploit this kind of access
Get information about the currently loaded configuration, including available workflows. It is categorised as a Read tool in the Qontinui MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qontinui MCP Server MCP server in PolicyLayer and add a rule for get_loaded_config: 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 Qontinui MCP Server. Nothing to install.
get_loaded_config 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_loaded_config 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_loaded_config. 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_loaded_config is provided by the Qontinui MCP Server MCP server (qontinui/qontinui-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 →