ntp_check
Check an NTP server: reachability and clock offset relative to local system time. Uses NTPv3 client packet over UDP. offset_seconds > 0 means server is ahead of local clock.
This record as markdown: /tools/aaronckj-mcp-nettools/ntp-check.md
What ntp_check does on Mcp Nettools
AI agents call ntp_check to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why ntp_check is rated Low
ntp_check retrieves diagnostic information about NTP server reachability and clock offset without modifying any state. It is purely a query/lookup operation analogous to ping or DNS lookup (other Read tools on this server). The tool has minimal blast radius—an agent cannot cause damage by querying NTP servers. Classification as Read is appropriate.
From the tool's definition Tool performs network diagnostics query: 'Check an NTP server: reachability and clock offset relative to local system time.' Uses read-only NTPv3 client packet over UDP to retrieve server status and timing information.
Attacks that exploit this kind of access
The rule that runs ntp_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ntp_check, this is the rule to start with:
ntp_check 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 Nettools, apply this rule, and every ntp_check call is checked against it from then on.
Questions about ntp_check
Check an NTP server: reachability and clock offset relative to local system time. Uses NTPv3 client packet over UDP. offset_seconds > 0 means server is ahead of local clock. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.
Register the Mcp Nettools MCP server in PolicyLayer and add a rule for ntp_check: 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 Nettools. Nothing to install.
ntp_check 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 ntp_check 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 ntp_check. 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.
ntp_check is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Nettools, and thousands of servers like it.
This server
Across the catalogue