datausa.reference.members
Look up the member values (e.g. specific states, counties, industries, or years) available for a dimension level within a Data USA cube, optionally filtered by name — use this to find the exact key to pass into datausa.data.query's include filter
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/datausa.reference.members.md
What datausa.reference.members does on Apibase
AI agents call datausa.reference.members to retrieve information from Apibase 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 |
|---|---|---|---|
cube | string | Yes | Data cube (dataset) name, e.g. "acs_yg_total_population_1". |
level | string | Yes | Dimension level name to list members for, e.g. "State" or "County". |
limit | integer | — | Maximum number of members to return. |
search | string | — | Filter members by name, case-insensitive substring match (e.g. "cali"). |
Parameters from the server's own tool schema.
Why datausa.reference.members is rated Low
Tool retrieves reference data for querying; no modifications, deletions, or external operations.
From the tool's definition Look up member values, find exact key, filtered by name
Attacks that exploit this kind of access
The rule that runs datausa.reference.members safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For datausa.reference.members, this is the rule to start with:
datausa.reference.members 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 Apibase, apply this rule, and every datausa.reference.members call is checked against it from then on.
Questions about datausa.reference.members
Look up the member values (e.g. specific states, counties, industries, or years) available for a dimension level within a Data USA cube, optionally filtered by name — use this to find the exact key to pass into datausa.data.query's include filter. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
datausa.reference.members accepts 4 parameters: cube, level, limit, search. Required: cube, level. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for datausa.reference.members: 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 Apibase. Nothing to install.
datausa.reference.members 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 datausa.reference.members 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 datausa.reference.members. 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.
datausa.reference.members is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue