spending.federal.agency
Search federal awards by agency name (e.g. "Defense", "NASA", "Health and Human Services"). Returns top awards by amount for a fiscal year. Source: USAspending.gov — covers all federal agencies.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/spending.federal.agency.md
What spending.federal.agency does on Apibase
AI agents call spending.federal.agency 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 top awards to return (1-25, default 10) |
agency_name | string | Yes | Federal agency name or keyword (e.g. "Defense", "NASA", "Health and Human Services") |
fiscal_year | integer | — | Fiscal year (e.g. 2025). Default: current year. |
Parameters from the server's own tool schema.
Why spending.federal.agency is rated Low
Tool retrieves and queries publicly available federal spending data without modification or side effects.
From the tool's definition Search federal awards by agency name. Returns top awards. Source: USAspending.gov
Attacks that exploit this kind of access
The rule that runs spending.federal.agency 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.agency, this is the rule to start with:
spending.federal.agency 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.agency call is checked against it from then on.
Questions about spending.federal.agency
Search federal awards by agency name (e.g. "Defense", "NASA", "Health and Human Services"). Returns top awards by amount for a fiscal year. Source: USAspending.gov — covers all federal agencies. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
spending.federal.agency accepts 3 parameters: limit, agency_name, fiscal_year. Required: agency_name. 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.agency: 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.agency 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.agency 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.agency. 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.agency 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