Check DNSSEC status for a domain.
AI agents call check_dnssec_status to retrieve information from BasicSec MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes DNSSEC validation status for a domain—a read-only security assessment with no side effects. It does not execute code, modify DNS records, delete data, or initiate financial transactions. The blast radius of misuse is minimal; an agent could only retrieve security status information, which is not sensitive enough to warrant higher severity classification.
From the tool's definition Tool name 'check_dnssec_status' and description 'Check DNSSEC status for a domain' indicate a query/verification operation.
Attacks that exploit this kind of access
Check DNSSEC status for a domain. It is categorised as a Read tool in the BasicSec MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BasicSec MCP Server MCP server in PolicyLayer and add a rule for check_dnssec_status: 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 BasicSec MCP Server. Nothing to install.
check_dnssec_status 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 check_dnssec_status 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 check_dnssec_status. 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.
check_dnssec_status is provided by the BasicSec MCP Server MCP server (marlinkcyber/basicsec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →