Get and validate DMARC record for a domain.
AI agents call get_dmarc_record 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 queries DNS records to retrieve and validate DMARC configuration data. It performs passive DNS lookups and validation checks without modifying any data, executing code, or causing side effects. This is a typical read operation for security analysis purposes, with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_dmarc_record' and description 'Get and validate DMARC record for a domain' indicate pure retrieval and analysis of DNS records. No modification, deletion, code execution, or financial operations are performed.
Attacks that exploit this kind of access
Get and validate DMARC record 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 get_dmarc_record: 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.
get_dmarc_record 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 get_dmarc_record 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 get_dmarc_record. 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.
get_dmarc_record 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 →