Low Risk

get_dnssec_ds_records

Fetch DS records for a DNSSEC-enabled domain (needed for registrar configuration)

How to control get_dnssec_ds_records ↓

What get_dnssec_ds_records does on cPanel MCP Server

AI agents call get_dnssec_ds_records to retrieve information from cPanel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_dnssec_ds_records needs a policy

This tool retrieves existing DNS delegation signer records for configuration purposes. No data is modified, deleted, executed, or financial transactions occur. It is purely informational and read-only.

From the tool's definition Tool name and description indicate it 'Fetch[es] DS records' — a retrieval operation with no side effects. DS records are public DNSSEC configuration data needed for registrar setup.

Documented attack patterns abuse exactly the kind of access get_dnssec_ds_records gives an agent:

How to control get_dnssec_ds_records

PolicyLayer is an MCP gateway — it sits between your AI agents and cPanel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_dnssec_ds_records:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_dnssec_ds_records": {}
  }
}

get_dnssec_ds_records is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register cPanel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_dnssec_ds_records

What does the get_dnssec_ds_records tool do? +

Fetch DS records for a DNSSEC-enabled domain (needed for registrar configuration). It is categorised as a Read tool in the cPanel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_dnssec_ds_records? +

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

What risk level is get_dnssec_ds_records? +

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

Can I rate-limit get_dnssec_ds_records? +

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

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

get_dnssec_ds_records is provided by the cPanel MCP Server MCP server (0xhayd3n/cpanel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every cPanel MCP Server tool call.

Start from cPanel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

164 cPanel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.