govinfo_legislation_committee_path
Return the complete committee and subcommittee path published in GovInfo Bill Status XML for one bill, preserving stable committee system codes, parent links, chambers, committee types, and dated activities. Use this for 'which committees handled H.R. 2?', 'show subcommittee referrals for this bi...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/govinfo-legislation-committee-path.md
What govinfo_legislation_committee_path does on Livedatalink
AI agents invoke govinfo_legislation_committee_path to trigger actions in Livedatalink. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
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_committee_path is rated High
govinfo_legislation_committee_path triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs govinfo_legislation_committee_path 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_committee_path, this is the rule to start with:
govinfo_legislation_committee_path stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 govinfo_legislation_committee_path call is checked against it from then on.
Questions about govinfo_legislation_committee_path
Return the complete committee and subcommittee path published in GovInfo Bill Status XML for one bill, preserving stable committee system codes, parent links, chambers, committee types, and dated activities. Use this for 'which committees handled H.R. 2?', 'show subcommittee referrals for this bill', or 'build a committee-routing audit trail'. Coverage is 118th-Congress HR/S only; absence means the captured XML supplied no committee record. It is categorised as a Execute tool in the Livedatalink MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
govinfo_legislation_committee_path 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.
Register the Livedatalink MCP server in PolicyLayer and add a rule for govinfo_legislation_committee_path: 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.
govinfo_legislation_committee_path is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the govinfo_legislation_committee_path 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 govinfo_legislation_committee_path. 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.
govinfo_legislation_committee_path 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