gov.district

Resolve a US street address to its congressional district (119th Congress), state, and county via the US Census Bureau geocoder. Returns matched address, lat/lon, state (name + abbr), county, and district number (null for at-large/delegate). The point-in-polygon district lookup an agent can\

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.district.md

WHAT IT DOES

What gov.district does on Mcp

AI agents call gov.district 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.district is rated Low

This tool retrieves and queries publicly available geographic and political boundary data from the US Census Bureau. It performs read-only geocoding and point-in-polygon lookups to map addresses to congressional districts. There are no side effects, data modifications, financial transactions, or code execution involved.

From the tool's definition Tool resolves a US street address to congressional district via US Census Bureau geocoder; returns matched address, lat/lon, state, county, and district number.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

gov.district Allowed

gov.district 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.district": {}
  }
}

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.district call is checked against it from then on.

FAQ

Questions about gov.district

What does the gov.district tool do? +

How do I enforce a policy on gov.district? +

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

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

Can I rate-limit gov.district? +

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

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

gov.district 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 →