gov.congress-member
US Congress member lookup by bioguide ID or filtered list (state, district, congress, currentMember). Bioguide IDs are stable across history.
This record as markdown: /tools/io-github-2s-io-mcp/gov.congress-member.md
What gov.congress-member does on Mcp
AI agents call gov.congress-member to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gov.congress-member is rated Low
This is a straightforward data retrieval tool that queries public biographical information about US Congress members. It supports filtering and lookup operations but produces no side effects, creates no data, executes no code, and cannot modify or delete information. The public nature of Congress member data further reduces risk.
From the tool's definition Tool performs 'lookup by bioguide ID or filtered list (state, district, congress, currentMember)' — purely retrieves public information about Congress members with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs gov.congress-member safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gov.congress-member, this is the rule to start with:
gov.congress-member 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 Mcp, apply this rule, and every gov.congress-member call is checked against it from then on.
Questions about gov.congress-member
US Congress member lookup by bioguide ID or filtered list (state, district, congress, currentMember). Bioguide IDs are stable across history. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for gov.congress-member: 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 Mcp. Nothing to install.
gov.congress-member 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 gov.congress-member 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 gov.congress-member. 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.
gov.congress-member is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue