util_robots_inspect
Read robots.txt rules and sitemap declarations before crawling or indexing a domain.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/util-robots-inspect.md
What util_robots_inspect does on Delx MCP Server
AI agents call util_robots_inspect to retrieve information from Delx MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Domain or URL to inspect |
timeout | integer | — | Timeout in seconds (1-15) |
Parameters from the server's own tool schema.
Why util_robots_inspect is rated Low
This tool performs a read-only operation that queries public web server configuration files (robots.txt and sitemaps). It retrieves information for inspection purposes before taking further action, with no capability to modify, delete, or execute arbitrary code. It is clearly a Read operation with minimal security risk if misused - an agent could at most gather information about a domain's crawling policies.
From the tool's definition The tool 'util_robots_inspect' reads and retrieves 'robots.txt rules and sitemap declarations' from a domain.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs util_robots_inspect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_robots_inspect, this is the rule to start with:
util_robots_inspect is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx MCP Server, apply this rule, and every util_robots_inspect call is checked against it from then on.
Questions about util_robots_inspect
Read robots.txt rules and sitemap declarations before crawling or indexing a domain. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
util_robots_inspect accepts 2 parameters: url, timeout. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for util_robots_inspect: 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 Delx MCP Server. Nothing to install.
util_robots_inspect 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 util_robots_inspect 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 util_robots_inspect. 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.
util_robots_inspect is provided by the Delx MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue