spending.federal.geography
Get total US federal spending by state for contracts, grants, or all awards in a fiscal year. Returns all 50+ states sorted by spending amount. Useful for regional economic analysis and policy research. Source: USAspending.gov.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/spending.federal.geography.md
What spending.federal.geography does on Apibase
AI agents call spending.federal.geography 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 |
|---|---|---|---|
award_type | string | — | Filter by award type: contracts, grants, or all (default: all) |
fiscal_year | integer | — | Fiscal year (e.g. 2025). Default: current year. |
Parameters from the server's own tool schema.
Why spending.federal.geography is rated Low
Tool retrieves and queries public federal spending data without modifying or executing operations.
From the tool's definition Get total US federal spending by state; returns data sorted by spending amount.
Attacks that exploit this kind of access
The rule that runs spending.federal.geography 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 spending.federal.geography, this is the rule to start with:
spending.federal.geography 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 spending.federal.geography call is checked against it from then on.
Questions about spending.federal.geography
Get total US federal spending by state for contracts, grants, or all awards in a fiscal year. Returns all 50+ states sorted by spending amount. Useful for regional economic analysis and policy research. Source: USAspending.gov. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
spending.federal.geography accepts 2 parameters: award_type, fiscal_year. 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 spending.federal.geography: 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.
spending.federal.geography 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 spending.federal.geography 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 spending.federal.geography. 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.
spending.federal.geography 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