spending_award_details
Get full detail for one federal award by its award id (the generated id from spending_search_awards): recipient, amount, type, awarding and funding agencies, period of performance, NAICS/PSC, place of performance, and description.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/spending-award-details.md
What spending_award_details does on Livedatalink
AI agents call spending_award_details to retrieve information from Livedatalink 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_id | string | Yes | Generated award id from spending_search_awards. |
Parameters from the server's own tool schema.
Why spending_award_details is rated Low
This tool retrieves and displays publicly available federal spending data by award ID. It has no side effects—it queries and returns information about existing federal awards without creating, modifying, deleting, or executing any operations. This is a classic Read operation with minimal risk when accessed by an AI agent.
From the tool's definition Tool description indicates it 'Get[s] full detail for one federal award' and lists retrievable fields: 'recipient, amount, type, awarding and funding agencies, period of performance, NAICS/PSC, place of performance, and description.' The verb 'Get' and the…
Attacks that exploit this kind of access
The rule that runs spending_award_details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spending_award_details, this is the rule to start with:
spending_award_details 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 Livedatalink, apply this rule, and every spending_award_details call is checked against it from then on.
Questions about spending_award_details
Get full detail for one federal award by its award id (the generated id from spending_search_awards): recipient, amount, type, awarding and funding agencies, period of performance, NAICS/PSC, place of performance, and description. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
spending_award_details accepts 1 parameter: award_id. Required: award_id. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for spending_award_details: 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 Livedatalink. Nothing to install.
spending_award_details 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_award_details 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_award_details. 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_award_details is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue