check_device_dns

A read tool on the 1Panel MCP server.

SERVER1Panel MCP Server SOURCEeaveluo/1panel-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/eaveluo-1panel-mcp/check-device-dns.md

WHAT IT DOES

What check_device_dns does on 1Panel MCP Server

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

RISK

Why check_device_dns is rated Low

This tool retrieves DNS information from the device for inspection purposes. There are no side effects, no data modification, no code execution, and no destructive operations. It is a read-only diagnostic query consistent with server monitoring capabilities mentioned in the server description.

From the tool's definition Tool name 'check_device_dns' and description 'Check device DNS' indicate a query operation that retrieves DNS configuration or status information. The verb 'check' implies inspection/verification without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_device_dns safely

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

check_device_dns Allowed

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

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

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

FAQ

Questions about check_device_dns

What does the check_device_dns tool do? +

check_device_dns is a read tool on the 1Panel MCP Server MCP server. It is categorised as a Read tool in the 1Panel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_device_dns? +

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

What risk level is check_device_dns? +

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

Can I rate-limit check_device_dns? +

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

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

check_device_dns is provided by the 1Panel MCP Server MCP server (eaveluo/1panel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 1Panel MCP Server, and thousands of servers like it.

This server

All 286 1Panel MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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