Query multiple PTR records in a single batch request
AI agents call thealeph_batch_query_ptr to retrieve information from The Aleph MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
PTR record lookups retrieve existing DNS data without creating, modifying, deleting, or executing anything. The batch query capability does not change this fundamental read-only nature. The tool falls squarely into the 'Read' category as it queries and retrieves network metadata. Severity is low because misuse would only expose publicly available DNS information without enabling destructive or financial harm.
From the tool's definition Tool description states 'Query multiple PTR records in a single batch request' — PTR (reverse DNS) record lookups are read-only network intelligence queries with no side effects.
Attacks that exploit this kind of access
Query multiple PTR records in a single batch request. It is categorised as a Read tool in the The Aleph MCP MCP Server, which means it retrieves data without modifying state.
Register the The Aleph MCP server in PolicyLayer and add a rule for thealeph_batch_query_ptr: 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 The Aleph MCP. Nothing to install.
thealeph_batch_query_ptr 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 thealeph_batch_query_ptr 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 thealeph_batch_query_ptr. 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.
thealeph_batch_query_ptr is provided by the The Aleph MCP server (nu-aqualab/thealeph-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 →