Make an HTTP HEAD request to retrieve only headers from the specified URL
AI agents call http_head to retrieve information from MCP-RQuest without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
HTTP HEAD requests only retrieve response headers with no body content and have no side effects on the target resource. This is a pure read/metadata operation. The only elevated concern is the server's stated capability to bypass anti-bot measures, but the HEAD method itself remains read-only and low-blast-radius.
From the tool's definition Make an HTTP HEAD request to retrieve only headers from the specified URL
Documented attack patterns abuse exactly the kind of access http_head gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-RQuest, and nothing reaches the server without passing your rules. This is the rule we recommend for http_head:
{
"version": "1",
"default": "deny",
"tools": {
"http_head": {}
}
}http_head is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Make an HTTP HEAD request to retrieve only headers from the specified URL. It is categorised as a Read tool in the MCP-RQuest MCP Server, which means it retrieves data without modifying state.
Register the MCP-RQuest MCP server in PolicyLayer and add a rule for http_head: 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-RQuest. Nothing to install.
http_head 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 http_head 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 http_head. 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.
http_head is provided by the MCP-RQuest MCP server (xxxbrian/mcp-rquest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 MCP-RQuest tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 MCP-RQuest tools catalogued and risk-classified — across an index of 42,500+ MCP servers.