Low Risk

lookup_domain_detailed

Return full host records for a domain (services, ASN, geo, TLS). Shows a limited sample of matching records.

How to control lookup_domain_detailed ↓

What lookup_domain_detailed does on MCP-Censys

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

Low Risk

Why lookup_domain_detailed needs a policy

This tool retrieves existing data from Censys about domain infrastructure without modifying, deleting, or executing anything. It falls squarely in the Read category. Severity is medium (not low) because reconnaissance data about network infrastructure and services can inform targeted attacks, even though the tool itself has no direct harmful capability.

From the tool's definition Tool returns 'full host records for a domain (services, ASN, geo, TLS)' with 'limited sample of matching records.' It explicitly retrieves and queries data with no modification, deletion, or execution capability.

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

How to control lookup_domain_detailed

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

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

lookup_domain_detailed 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 MCP-Censys — 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 lookup_domain_detailed

What does the lookup_domain_detailed tool do? +

Return full host records for a domain (services, ASN, geo, TLS). Shows a limited sample of matching records. It is categorised as a Read tool in the MCP-Censys MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lookup_domain_detailed? +

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

What risk level is lookup_domain_detailed? +

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

Can I rate-limit lookup_domain_detailed? +

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

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

lookup_domain_detailed is provided by the MCP-Censys MCP server (nickpending/mcp-censys). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP-Censys tool call.

Start from MCP-Censys, 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.

5 MCP-Censys 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.