govcon_fetch_vendor_contract_history

SERVERDataNexus MCP SOURCEdev-7bd0/mcp-server

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-7bd0-mcp-server/govcon-fetch-vendor-contract-history.md

WHAT IT DOES

What govcon_fetch_vendor_contract_history does on DataNexus MCP

AI agents call govcon_fetch_vendor_contract_history to retrieve information from DataNexus MCP 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
`vendor_name`	string	—	Vendor or company name to search e.g. Booz Allen Hamilton. Required.
`jurisdiction`	string	—	Jurisdiction: US, EU, or UK. Default US. Optional.

Parameters from the server's own tool schema.

RISK

Why govcon_fetch_vendor_contract_history is rated Low

This tool retrieves and queries publicly available federal contract information without modifying, executing, or deleting any data. The read-only guarantee and idempotent nature confirm no side effects. Low severity because misuse only risks unauthorized information gathering about public government contracts, not system compromise or data destruction.

From the tool's definition Tool description explicitly states: 'Read-only. No side effects. Idempotent.' Fetches historical contract data from verified public source (USASpending.gov). Returns aggregate information: total award value, top agencies, contract types, and award dates.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs govcon_fetch_vendor_contract_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and DataNexus MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For govcon_fetch_vendor_contract_history, this is the rule to start with:

govcon_fetch_vendor_contract_history Allowed

govcon_fetch_vendor_contract_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "govcon_fetch_vendor_contract_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect DataNexus MCP, apply this rule, and every govcon_fetch_vendor_contract_history call is checked against it from then on.

FAQ

Questions about govcon_fetch_vendor_contract_history

What does the govcon_fetch_vendor_contract_history tool do? +

Fetch the complete federal contract award history for a specific vendor. Read-only. No side effects. Idempotent. vendor_name: Company or organisation name e.g. Booz Allen Hamilton. Required. Fuzzy match used. jurisdiction: One of US, EU, or UK. Optional. Default US. Returns total award value, top awarding agencies, contract types, and recent awards with amounts and dates. Use this when researching a specific company's government contracting history. Use govcon_search_contract_awards instead when exploring a topic area without a specific vendor. Verified source: USASpending.gov. 4-hour cache. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="govcon_fetch_vendor_contract_history", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}". It is categorised as a Read tool in the DataNexus MCP MCP Server, which means it retrieves data without modifying state.

What parameters does govcon_fetch_vendor_contract_history accept? +

govcon_fetch_vendor_contract_history accepts 2 parameters: vendor_name, jurisdiction. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on govcon_fetch_vendor_contract_history? +

Register the DataNexus MCP server in PolicyLayer and add a rule for govcon_fetch_vendor_contract_history: 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 DataNexus MCP. Nothing to install.

What risk level is govcon_fetch_vendor_contract_history? +

govcon_fetch_vendor_contract_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit govcon_fetch_vendor_contract_history? +

Yes. Add a rate_limit block to the govcon_fetch_vendor_contract_history 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.

How do I block govcon_fetch_vendor_contract_history completely? +

Set action: deny in the PolicyLayer policy for govcon_fetch_vendor_contract_history. 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.

What MCP server provides govcon_fetch_vendor_contract_history? +

govcon_fetch_vendor_contract_history is provided by the DataNexus MCP server (dev-7bd0/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on DataNexus, and thousands of servers like it.

This server

All 55 DataNexus tools →

Across the catalogue

fetch_url on 0sec → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →