regulatory_fetch_docket_details

SERVERDataNexus MCP SOURCEdev-7bd0/mcp-server

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-7bd0-mcp-server/regulatory-fetch-docket-details.md

WHAT IT DOES

What regulatory_fetch_docket_details does on DataNexus MCP

AI agents call regulatory_fetch_docket_details to retrieve information from DataNexus MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`docket_id`	string	—	Docket ID e.g. EPA-HQ-OAR-2021-0668. Required.

Parameters from the server's own tool schema.

RISK

Why regulatory_fetch_docket_details is rated Low

This tool retrieves public regulatory docket information (title, agency, status, dates, documents) from Regulations.gov and Federal Register. It performs no data modification, deletion, or external actions—purely informational queries against public government databases. The read-only nature, explicit idempotency guarantee, and focus on public data retrieval place this squarely in the Read category with low severity.

From the tool's definition Fetch full details for a specific regulatory docket by ID. Read-only. No side effects. Idempotent.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs regulatory_fetch_docket_details safely

PolicyLayer is an MCP gateway: it sits between your AI agents and DataNexus MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For regulatory_fetch_docket_details, this is the rule to start with:

regulatory_fetch_docket_details Allowed

regulatory_fetch_docket_details 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": {
    "regulatory_fetch_docket_details": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect DataNexus MCP, apply this rule, and every regulatory_fetch_docket_details call is checked against it from then on.

FAQ

Questions about regulatory_fetch_docket_details

What does the regulatory_fetch_docket_details tool do? +

Fetch full details for a specific regulatory docket by ID. Read-only. No side effects. Idempotent. US federal only. docket_id: Docket identifier in agency format e.g. EPA-HQ-OAR-2021-0317 or FTC-2024-0041. Required. Timeout is 30 seconds — large dockets may be slow. Returns docket title, agency, status, comment period dates, total comment count, and list of related documents. Use this when you have a docket ID from a search. Use regulatory_search_open_rulemakings instead when you need to find dockets by topic first. Verified source: Regulations.gov + Federal Register fallback. 4-hour cache. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="regulatory_fetch_docket_details", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}". It is categorised as a Read tool in the DataNexus MCP MCP Server, which means it retrieves data without modifying state.

What parameters does regulatory_fetch_docket_details accept? +

regulatory_fetch_docket_details accepts 1 parameter: docket_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on regulatory_fetch_docket_details? +

Register the DataNexus MCP server in PolicyLayer and add a rule for regulatory_fetch_docket_details: 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 DataNexus MCP. Nothing to install.

What risk level is regulatory_fetch_docket_details? +

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

Can I rate-limit regulatory_fetch_docket_details? +

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

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

regulatory_fetch_docket_details is provided by the DataNexus MCP server (dev-7bd0/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on DataNexus, and thousands of servers like it.

This server

All 55 DataNexus tools →

Across the catalogue

fetch_url on 0sec → The MCP Attack Database →

Guides

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