util_http_headers_inspect
Inspect security, cache, redirect, and server headers to audit a URL quickly.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/util-http-headers-inspect.md
What util_http_headers_inspect does on Delx Mcp A2a
AI agents call util_http_headers_inspect to retrieve information from Delx Mcp A2a 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 | URL to inspect |
timeout | integer | — | Timeout in seconds (1-15) |
Parameters from the server's own tool schema.
Why util_http_headers_inspect is rated Low
This tool retrieves and examines HTTP headers from a URL for auditing purposes. It performs no modifications to data, executes no code, and triggers no external operations beyond a standard HTTP HEAD or GET request. The action is purely informational inspection, placing it squarely in the Read category with low severity.
From the tool's definition Tool name 'util_http_headers_inspect' and description 'Inspect security, cache, redirect, and server headers to audit a URL quickly' indicates read-only header inspection with no modification or execution capabilities.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs util_http_headers_inspect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_http_headers_inspect, this is the rule to start with:
util_http_headers_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 A2a, apply this rule, and every util_http_headers_inspect call is checked against it from then on.
Questions about util_http_headers_inspect
Inspect security, cache, redirect, and server headers to audit a URL quickly. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
util_http_headers_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 A2a MCP server in PolicyLayer and add a rule for util_http_headers_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 A2a. Nothing to install.
util_http_headers_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_http_headers_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_http_headers_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_http_headers_inspect is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue