spending_recipient_summary
Summarize a company's federal awards: total dollars and top awards for a recipient name in a category (contracts by default). Useful for due diligence and to see who the government pays.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/spending-recipient-summary.md
What spending_recipient_summary does on Livedatalink
AI agents call spending_recipient_summary 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 |
|---|---|---|---|
limit | number | — | Top awards to list (default 5, max 25). |
category | string | — | Award category: 'contracts' (default), 'grants', 'loans', or 'other'. |
recipient | string | Yes | Recipient company/org name. |
Parameters from the server's own tool schema.
Why spending_recipient_summary is rated Low
This tool queries and aggregates publicly available federal spending data. It retrieves information about government contracts and awards, presenting summaries of financial data for analysis. There are no side effects, state changes, code execution, destructive actions, or financial transactions involved. It is a straightforward read/query operation.
From the tool's definition The tool 'summarize[s] a company's federal awards' and is described as useful for 'due diligence and to see who the government pays.' The verbs are 'summarize' and 'see' — pure data retrieval operations with no mutation, deletion, or side effects.
Attacks that exploit this kind of access
The rule that runs spending_recipient_summary 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_recipient_summary, this is the rule to start with:
spending_recipient_summary 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_recipient_summary call is checked against it from then on.
Questions about spending_recipient_summary
Summarize a company's federal awards: total dollars and top awards for a recipient name in a category (contracts by default). Useful for due diligence and to see who the government pays. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
spending_recipient_summary accepts 3 parameters: limit, category, recipient. Required: recipient. 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_recipient_summary: 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_recipient_summary 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_recipient_summary 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_recipient_summary. 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_recipient_summary 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