gov.congress-record

Daily Congressional Record issues (official US House+Senate proceedings transcript) via Congress.gov. Filter by year/month/day.

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/gov.congress-record.md

WHAT IT DOES

What gov.congress-record does on Mcp

AI agents call gov.congress-record 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.

RISK

Why gov.congress-record is rated Low

This tool queries and retrieves publicly available historical congressional proceedings data. It performs a straightforward read operation (search/fetch) of official government records with no side effects, data modification, code execution, or financial transactions involved.

From the tool's definition Tool provides access to 'Daily Congressional Record issues (official US House+Senate proceedings transcript)' with filtering by time periods.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gov.congress-record 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-record, this is the rule to start with:

gov.congress-record Allowed

gov.congress-record is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gov.congress-record": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every gov.congress-record call is checked against it from then on.

FAQ

Questions about gov.congress-record

What does the gov.congress-record tool do? +

Daily Congressional Record issues (official US House+Senate proceedings transcript) via Congress.gov. Filter by year/month/day. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gov.congress-record? +

Register the MCP server in PolicyLayer and add a rule for gov.congress-record: 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.

What risk level is gov.congress-record? +

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

Can I rate-limit gov.congress-record? +

Yes. Add a rate_limit block to the gov.congress-record 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 gov.congress-record completely? +

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

gov.congress-record 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.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →