spending.federal.awards
Search 60M+ US federal contract and grant awards by keyword, recipient, or NAICS code. Returns award amount, recipient, agency, dates, and description. Sorted by amount descending. Source: USAspending.gov (DATA Act mandate, US Gov open data).
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/spending.federal.awards.md
What spending.federal.awards does on Apibase
AI agents call spending.federal.awards 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 |
|---|---|---|---|
limit | integer | — | Number of results to return (1-25, default 10) |
keyword | string | Yes | Search keyword for federal awards (e.g. "artificial intelligence", "cybersecurity", company name) |
award_type | string | — | Filter by award type: contracts, grants, or all (default: all) |
fiscal_year | integer | — | Fiscal year to filter (e.g. 2025). Default: current year. |
Parameters from the server's own tool schema.
Why spending.federal.awards is rated Low
Tool retrieves public federal spending data with no side effects or modifications.
From the tool's definition Search 60M+ federal contract and grant awards by keyword, recipient, or NAICS code.
Attacks that exploit this kind of access
The rule that runs spending.federal.awards 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.awards, this is the rule to start with:
spending.federal.awards 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.awards call is checked against it from then on.
Questions about spending.federal.awards
Search 60M+ US federal contract and grant awards by keyword, recipient, or NAICS code. Returns award amount, recipient, agency, dates, and description. Sorted by amount descending. Source: USAspending.gov (DATA Act mandate, US Gov open data). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
spending.federal.awards accepts 4 parameters: limit, keyword, award_type, fiscal_year. Required: keyword. 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.awards: 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.awards 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.awards 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.awards. 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.awards 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