This record as markdown: /tools/io-github-2s-io-mcp/gov.congress-filings.md
What gov.congress-filings does on Mcp
AI agents call gov.congress-filings 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-filings is rated Low
This tool queries public government data about US House members and their filings. It retrieves or searches information without side effects, making it a Read operation. The data is public record and tracking/viewing it poses minimal risk. Severity is low given the absence of write, execution, or financial capabilities.
From the tool's definition Tool name 'gov.congress-filings' and description 'Track US House members' indicate data retrieval without modification or triggering external operations.
Attacks that exploit this kind of access
The rule that runs gov.congress-filings 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-filings, this is the rule to start with:
gov.congress-filings 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-filings call is checked against it from then on.
Questions about gov.congress-filings
Track US House members. 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-filings: 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-filings 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-filings 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-filings. 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-filings 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