congress_house_votes
List recent U.S. House roll-call votes for a Congress, with vote number, question, result, and date. Defaults to the current Congress.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/congress-house-votes.md
What congress_house_votes does on Livedatalink
AI agents call congress_house_votes 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 | — | Max votes (default 20). |
congress | number | — | Congress number (default current, 91). |
Parameters from the server's own tool schema.
Why congress_house_votes is rated Low
This tool retrieves and queries publicly available legislative voting records. It performs no data creation, modification, deletion, code execution, or financial operations. The read-only nature and public domain nature of the data make this a low-severity Read operation.
From the tool's definition Tool description states 'List recent U.S. House roll-call votes' - a retrieval operation with no modification capability. Public congressional voting records are already publicly available and contain no sensitive data requiring protection.
Attacks that exploit this kind of access
The rule that runs congress_house_votes 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 congress_house_votes, this is the rule to start with:
congress_house_votes 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 congress_house_votes call is checked against it from then on.
Questions about congress_house_votes
List recent U.S. House roll-call votes for a Congress, with vote number, question, result, and date. Defaults to the current Congress. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
congress_house_votes accepts 2 parameters: limit, congress. 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 congress_house_votes: 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.
congress_house_votes 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 congress_house_votes 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 congress_house_votes. 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.
congress_house_votes 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