datausa.reference.cubes
Browse the 120+ data cubes (datasets) available on Data USA — population, income, education, employment, housing, and more. List cube names filterable by topic or keyword, or fetch full detail (available dimension levels and measures) for one specific cube by name, to plan a datausa.data.query call
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/datausa.reference.cubes.md
What datausa.reference.cubes does on Apibase
AI agents call datausa.reference.cubes 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 | — | Exact cube name to get full detail for (dimensions, levels, measures). Omit to list all available cubes instead. |
limit | integer | — | When listing cubes: maximum number of cubes to return (default 50, max 200). |
topic | string | — | When listing cubes: filter by topic, case-insensitive substring match (e.g. "Education", "Diversity"). Ignored when cube is set. |
search | string | — | When listing cubes: filter by cube name or dataset name, case-insensitive substring match. Ignored when cube is set. |
Parameters from the server's own tool schema.
Why datausa.reference.cubes is rated Low
Tool queries and lists available datasets without modifying or executing operations.
From the tool's definition Browse, List cube names, fetch full detail — retrieves data
Attacks that exploit this kind of access
The rule that runs datausa.reference.cubes 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.cubes, this is the rule to start with:
datausa.reference.cubes 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.cubes call is checked against it from then on.
Questions about datausa.reference.cubes
Browse the 120+ data cubes (datasets) available on Data USA — population, income, education, employment, housing, and more. List cube names filterable by topic or keyword, or fetch full detail (available dimension levels and measures) for one specific cube by name, to plan a datausa.data.query call. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
datausa.reference.cubes accepts 4 parameters: cube, limit, topic, search. 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.cubes: 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.cubes 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.cubes 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.cubes. 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.cubes 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