Makes an HTTP HEAD request via curl and returns structured response headers (no body). Use to check resource existence, content type, or cache headers.
AI agents call head to retrieve information from Make without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
An HTTP HEAD request is a read-only operation that retrieves metadata/headers without a body and has no side effects on the target resource. It is purely informational.
From the tool's definition Makes an HTTP HEAD request via curl and returns structured response headers (no body). Use to check resource existence, content type, or cache headers.
Documented attack patterns abuse exactly the kind of access head gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for head:
{
"version": "1",
"default": "deny",
"tools": {
"head": {}
}
}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.
Makes an HTTP HEAD request via curl and returns structured response headers (no body). Use to check resource existence, content type, or cache headers. It is categorised as a Read tool in the Make MCP Server, which means it retrieves data without modifying state.
Register the Make MCP server in PolicyLayer and add a rule for 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 Make. Nothing to install.
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 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 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.
head is provided by the Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Make, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.