Low Risk

ptr_lookup

Reverse DNS lookup. Find the hostname associated with an IP address. A valid PTR record is important for email sending reputation.

Part of the Mailx Tools server.

ptr_lookup is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MAILX TOOLS →

Free to start. No card required.

AI agents call ptr_lookup to retrieve information from Mailx Tools without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though ptr_lookup only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

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

See the full Mailx Tools policy for all 16 tools.

Get this rule live on your own Mailx Tools server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MAILX TOOLS →

View all 16 tools →

These attack patterns abuse exactly the kind of access ptr_lookup gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so ptr_lookup only ever does what you allow.

SECURE MAILX TOOLS →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the ptr_lookup tool do? +

Reverse DNS lookup. Find the hostname associated with an IP address. A valid PTR record is important for email sending reputation.. It is categorised as a Read tool in the Mailx Tools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ptr_lookup? +

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

What risk level is ptr_lookup? +

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

Can I rate-limit ptr_lookup? +

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

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

ptr_lookup is provided by the Mailx Tools MCP server (mailwarm/mailx-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mailx Tools tool call.

Deterministic rules across all 16 Mailx Tools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.