congress_member_details
Get detailed profile for one member of Congress by bioguide ID (e.g. 'P000197'), including party history, terms served, and leadership roles.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/congress-member-details.md
What congress_member_details does on Livedatalink
AI agents call congress_member_details 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 |
|---|---|---|---|
bioguide_id | string | Yes | Bioguide ID, e.g. 'P000197'. |
Parameters from the server's own tool schema.
Why congress_member_details is rated Low
This is a straightforward data retrieval operation on public congressional records. It queries and returns information about elected officials with no side effects, no data modification, and no ability to trigger external actions. The worst-case misuse (e.g., scraping all members) would be rate-limiting or ToS violations, not a security or safety issue. Hence low severity.
From the tool's definition Tool retrieves 'detailed profile for one member of Congress' including 'party history, terms served, and leadership roles' — all publicly available biographical data with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs congress_member_details 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_member_details, this is the rule to start with:
congress_member_details 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_member_details call is checked against it from then on.
Questions about congress_member_details
Get detailed profile for one member of Congress by bioguide ID (e.g. 'P000197'), including party history, terms served, and leadership roles. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
congress_member_details accepts 1 parameter: bioguide_id. Required: bioguide_id. 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_member_details: 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_member_details 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_member_details 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_member_details. 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_member_details 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