get_everything_report

Generate the complete live IntoDNS.ai report covering DNS, email authentication, web/HTTPS, blacklist reputation, sender requirements, and canonical citation URLs in a single call. Read-only, no domain mutation. ~5-15s latency depending on backend cache state. Use when the user asks for everythin...

Server Intodns rosconl/intodns-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_everything_report does on Intodns

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

Why get_everything_report needs a policy

This tool performs information retrieval and analysis only. It queries existing DNS records and security configurations to generate a comprehensive report, with no capability to create, modify, delete, or execute operations. The explicit statement that it is 'read-only' with 'no side effects' confirms it belongs in the Read category with low severity risk.

From the tool's definition Tool description explicitly states 'Read-only, no domain mutation' and 'No auth, no side effects.' The tool 'Generate[s] the complete live IntoDNS.ai report' by querying DNS, email authentication, and blacklist data without modifying any state.

Questions about get_everything_report

What does the get_everything_report tool do? +

Generate the complete live IntoDNS.ai report covering DNS, email authentication, web/HTTPS, blacklist reputation, sender requirements, and canonical citation URLs in a single call. Read-only, no domain mutation. ~5-15s latency depending on backend cache state. Use when the user asks for everything, the full picture, or a deep current-state summary; use scan_domain for a faster default scan, or create_report_snapshot when the result must remain immutable for audit/ticket use. No auth, no side effects. It is categorised as a Read tool in the Intodns MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_everything_report? +

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

What risk level is get_everything_report? +

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

Can I rate-limit get_everything_report? +

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

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

get_everything_report is provided by the Intodns MCP server (rosconl/intodns-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.