govinfo_legislation_search

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Low RISK CLASS

Category Read

Parameters 81 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/govinfo-legislation-search.md

WHAT IT DOES

What govinfo_legislation_search does on Livedatalink

AI agents call govinfo_legislation_search 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`	integer	—	Maximum bills. Default 20.
`query`	string	Yes	Bill number/title phrase, sponsor name, policy area, subject, or committee phrase.
`offset`	integer	—	Bills to skip. Default 0.
`bill_type`	string	—	Hosted measure type: HR for a House bill or S for a Senate bill. Resolutions are outside this v1 snapshot.
`policy_area`	string	—	Optional exact policy-area label, case-insensitive.
`enacted_only`	boolean	—	When true, require at least one law citation in the captured Bill Status XML.
`response_format`	string	—	Human-readable markdown or machine-readable JSON. Default markdown.
`multiple_text_versions_only`	boolean	—	When true, require at least two published GovInfo text-version links.

Parameters from the server's own tool schema.

RISK

Why govinfo_legislation_search is rated Low

Even though govinfo_legislation_search only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs govinfo_legislation_search 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 govinfo_legislation_search, this is the rule to start with:

govinfo_legislation_search Allowed

govinfo_legislation_search 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": {
    "govinfo_legislation_search": {}
  }
}

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

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

FAQ

Questions about govinfo_legislation_search

What does the govinfo_legislation_search tool do? +

Search LiveDataLink's self-hosted official GovInfo Bill Status snapshot across bill number/title, all published titles, sponsor, policy area, legislative subjects, and committee names, with optional enacted and multi-version filters. Returns stable bill identifiers, sponsor/status facts, pagination, source XML hashes, and provenance. Use this for 'find 118th Congress bills about aviation safety', 'which border bills became law?', or 'bills assigned to the Finance Committee with multiple text versions'. Coverage is complete for HR and S in the 118th Congress only; resolutions and other Congresses are excluded. For Congress.gov's live/current API view, use the existing Congress tools instead. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does govinfo_legislation_search accept? +

govinfo_legislation_search accepts 8 parameters: limit, query, offset, bill_type, policy_area, enacted_only, response_format, multiple_text_versions_only. Required: query. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on govinfo_legislation_search? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for govinfo_legislation_search: 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.

What risk level is govinfo_legislation_search? +

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

Can I rate-limit govinfo_legislation_search? +

Yes. Add a rate_limit block to the govinfo_legislation_search 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 govinfo_legislation_search completely? +

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

govinfo_legislation_search 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.

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 381 Livedatalink tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

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