Check a domain
AI agents call tls_rpt_check to retrieve information from Domain Security without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves TLS-RPT (TLS Report) security information about a domain's TLS configuration and reporting policies. It performs no writes, deletions, code execution, or financial operations. The 'check' operation is fundamentally a read/query action that audits existing domain security posture. No API key requirement further confirms it is a passive audit tool.
From the tool's definition Tool name 'tls_rpt_check' and description 'Check a domain' indicate a query/audit operation. Context shows this is part of a domain security audit suite (alongside analyze_email_headers, dkim_check, dmarc_check, dns_lookup, dnssec_check) that retrieves and…
Attacks that exploit this kind of access
Check a domain. It is categorised as a Read tool in the Domain Security MCP Server, which means it retrieves data without modifying state.
Register the Domain Security MCP server in PolicyLayer and add a rule for tls_rpt_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 Domain Security. Nothing to install.
tls_rpt_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 tls_rpt_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 tls_rpt_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.
tls_rpt_check is provided by the Domain Security MCP server (ortamarco/domain-security-mcp-server). 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 →