bea.industry.value_added
Retrieve value added by NAICS industry sector from the BEA GDP by Industry dataset (Table 1, billions of dollars). Shows how much each industry contributes to total US GDP. Covers all major NAICS sectors: agriculture, mining, utilities, construction, manufacturing, wholesale/retail, information, ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/bea.industry.value-added.md
What bea.industry.value_added does on Apibase
AI agents call bea.industry.value_added 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 |
|---|---|---|---|
year | string | — | Year(s) to retrieve. Single year (e.g. "2023"), comma-separated list ("2021,2022,2023"), "LAST5" for latest 5 years, "LAST10" for latest 10, or "X"/"ALL" for al |
industry | string | — | Industry NAICS code(s) to retrieve. "ALL" (default) returns all industries. Common codes: "11"=Agriculture, "21"=Mining, "22"=Utilities, "23"=Construction, "31- |
frequency | string | — | Data frequency: A=Annual (default), Q=Quarterly. |
Parameters from the server's own tool schema.
Why bea.industry.value_added is rated Low
Tool queries and retrieves historical economic data with no side effects or modifications.
From the tool's definition Retrieve value added by NAICS industry sector from BEA GDP dataset
Attacks that exploit this kind of access
The rule that runs bea.industry.value_added 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 bea.industry.value_added, this is the rule to start with:
bea.industry.value_added 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 bea.industry.value_added call is checked against it from then on.
Questions about bea.industry.value_added
Retrieve value added by NAICS industry sector from the BEA GDP by Industry dataset (Table 1, billions of dollars). Shows how much each industry contributes to total US GDP. Covers all major NAICS sectors: agriculture, mining, utilities, construction, manufacturing, wholesale/retail, information, finance, real estate, healthcare, and government. Annual or quarterly frequency. Use for industry-level economic analysis and sector benchmarking. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
bea.industry.value_added accepts 3 parameters: year, industry, frequency. 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 bea.industry.value_added: 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.
bea.industry.value_added 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 bea.industry.value_added 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 bea.industry.value_added. 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.
bea.industry.value_added 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