Server metadata, dataset statistics, data freshness, and provenance information. Call this first in any session to verify data coverage, currency (last update check date), and content basis before relying on results for compliance decisions. Output: { server, version, dataset: { regulations, sect...
Part of the Us Regulations MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use about to create or modify resources in Us Regulations. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call about repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Us Regulations.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
about:
rules:
- action: allow
rate_limit:
max: 30
window: 60 See the full Us Regulations policy for all 10 tools.
Server metadata, dataset statistics, data freshness, and provenance information. Call this first in any session to verify data coverage, currency (last update check date), and content basis before relying on results for compliance decisions. Output: { server, version, dataset: { regulations, sections, built, freshness }, provenance }.. It is categorised as a Write tool in the Us Regulations MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for about. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Us Regulations MCP server.
about is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the about rule in your Intercept 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 Intercept policy for about. 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.
about is provided by the Us Regulations MCP server (@ansvar/us-regulations-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept