law.usc-section
Fetch the authoritative current text of a United States Code section by title + section number (e.g. title 17, section 107 = fair use). Returns citation, heading, hierarchy context, full statutory text, Statutes-at-Large source credit, and the official OLRC link; includeNotes adds amendment histo...
This record as markdown: /tools/io-github-2s-io-mcp/law.usc-section.md
What law.usc-section does on Mcp
AI agents call law.usc-section 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 law.usc-section is rated Low
This is a straightforward lookup tool that queries and returns public-domain statutory information. It has no side effects, cannot modify data, execute code, delete resources, or move money. The confidence is high because the description clearly indicates read-only retrieval ('Fetch', 'Returns') of reference material.
From the tool's definition Tool fetches and returns authoritative text of US Code sections—'Fetch the authoritative current text', 'Returns citation, heading, hierarchy context, full statutory text'—with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs law.usc-section 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 law.usc-section, this is the rule to start with:
law.usc-section 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 law.usc-section call is checked against it from then on.
Questions about law.usc-section
Fetch the authoritative current text of a United States Code section by title + section number (e.g. title 17, section 107 = fair use). Returns citation, heading, hierarchy context, full statutory text, Statutes-at-Large source credit, and the official OLRC link; includeNotes adds amendment history. Handles hyphenated/lettered sections like 1395w-4 or 78j. Verify statutory citations instead of relying on model memory. Public-domain. 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 law.usc-section: 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.
law.usc-section 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 law.usc-section 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 law.usc-section. 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.
law.usc-section 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