New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

govinfo_legislation_version_lineage

Return every published GovInfo text-version link for one hosted bill, including version type/code, date, immutable package identifier, package page, and official XML URL. Use this for 'show the introduced, reported, engrossed, enrolled, and law versions of H.R. 2670', 'what version codes exist fo...

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp
Low RISK CLASS
Category Read
Parameters 32 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-version-lineage.md

What govinfo_legislation_version_lineage does on Livedatalink

AI agents call govinfo_legislation_version_lineage 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.

ParameterTypeRequiredDescription
bill_type string Yes Hosted measure type: HR for a House bill or S for a Senate bill. Resolutions are outside this v1 snapshot.
bill_number integer Yes Numeric bill number within the fixed 118th Congress.
response_format string — Human-readable markdown or machine-readable JSON. Default markdown.

Parameters from the server's own tool schema.

Why govinfo_legislation_version_lineage is rated Low

Even though govinfo_legislation_version_lineage 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.

Risk signalsBulk/mass operation — affects multiple targets

Questions about govinfo_legislation_version_lineage

What does the govinfo_legislation_version_lineage tool do? +

Return every published GovInfo text-version link for one hosted bill, including version type/code, date, immutable package identifier, package page, and official XML URL. Use this for 'show the introduced, reported, engrossed, enrolled, and law versions of H.R. 2670', 'what version codes exist for S. 1?', or to assemble a reproducible legislative-text lineage. This is version metadata, not a text diff. Coverage is 118th-Congress HR/S only. 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_version_lineage accept? +

govinfo_legislation_version_lineage accepts 3 parameters: bill_type, bill_number, response_format. Required: bill_type, bill_number. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on govinfo_legislation_version_lineage? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for govinfo_legislation_version_lineage: 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_version_lineage? +

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

Can I rate-limit govinfo_legislation_version_lineage? +

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

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

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Livedatalink's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.