list_families
Use when the agent wants to enumerate the probe families codeitall has covered — typically before constructing a compare_implementations(task=…) call, or to recover from a typo flagged by compare_implementations's near-miss diagnostics. Returns the canonical family list with one-line descriptions...
This record as markdown: /tools/dev-codeitall-codeitall/list-families.md
What list_families does on Codeitall
AI agents call list_families to retrieve information from Codeitall 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 |
|---|---|---|---|
language | string | — |
Parameters from the server's own tool schema.
Why list_families is rated Low
This tool performs a pure query/retrieval operation to list available probe families and their metadata. It has no capability to modify data, execute operations, delete resources, or affect financial systems. The primary use case stated is enumerating families "before constructing" calls to other tools, making it clearly informational/preparatory in nature.
From the tool's definition Tool description states it "enumerate[s] the probe families" and "Returns the canonical family list with one-line descriptions, per-family counts, and the registered sub-family tags." The action is retrieving and listing metadata about available families with…
Attacks that exploit this kind of access
The rule that runs list_families safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Codeitall, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_families, this is the rule to start with:
list_families 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 Codeitall, apply this rule, and every list_families call is checked against it from then on.
Questions about list_families
Use when the agent wants to enumerate the probe families codeitall has covered — typically before constructing a compare_implementations(task=…) call, or to recover from a typo flagged by compare_implementations's near-miss diagnostics. Returns the canonical family list with one-line descriptions, per-family counts, and the registered sub-family tags (Phase 1.12 W5; pass any as subfamily to compare_implementations): { families: [{ name, description, n_implementations, n_observations, sub_families }, …] }. The family names returned here are exactly the strings accepted by compare_implementations. No required parameters. It is categorised as a Read tool in the Codeitall MCP Server, which means it retrieves data without modifying state.
list_families accepts 1 parameter: language. The full parameter table on this page comes from the server's own tool schema.
Register the Codeitall MCP server in PolicyLayer and add a rule for list_families: 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 Codeitall. Nothing to install.
list_families 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_families 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_families. 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_families is provided by the Codeitall MCP server (https://api.codeitall.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Codeitall, and thousands of servers like it.
This server
Across the catalogue