list_conditions
List organizational conditions (identity, label, guide count, causal-role counts). Filter by draft domain, subdomain, or causal_role (driver|mediator|outcome). Names and counts only — no addresses, no passages.
This record as markdown: /tools/com-aiengineerprofessional-guide-registry/list-conditions.md
What list_conditions does on Guide Registry
AI agents call list_conditions to retrieve information from Guide Registry without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | — | Substring match on the condition label. |
id | string | — | Exact condition_identity_id. When set, other filters are ignored. |
limit | number | — | Cap rows returned. Default 100, max 500. |
domain | string | — | Draft domain slug, e.g. organizational-structure-and-culture. |
subdomain | string | — | Draft sub-domain slug, e.g. organizational-learning-and-improvement. |
causal_role | string | — | driver | mediator | outcome. Unknown values match nothing. |
Parameters from the server's own tool schema.
Why list_conditions is rated Low
Even though list_conditions only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_conditions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Guide Registry, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_conditions, this is the rule to start with:
list_conditions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Guide Registry, apply this rule, and every list_conditions call is checked against it from then on.
Questions about list_conditions
List organizational conditions (identity, label, guide count, causal-role counts). Filter by draft domain, subdomain, or causal_role (driver|mediator|outcome). Names and counts only — no addresses, no passages. It is categorised as a Read tool in the Guide Registry MCP Server, which means it retrieves data without modifying state.
list_conditions accepts 6 parameters: q, id, limit, domain, subdomain, causal_role. The full parameter table on this page comes from the server's own tool schema.
Register the Guide Registry MCP server in PolicyLayer and add a rule for list_conditions: 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 Guide Registry. Nothing to install.
list_conditions 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 list_conditions 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 list_conditions. 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.
list_conditions is provided by the Guide Registry MCP server (https://aiengineerprofessional.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Guide Registry, and thousands of servers like it.
This server
Across the catalogue