util_header_map_normalize
Lowercase HTTP header keys and drop hop-by-hop headers
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/util-header-map-normalize.md
What util_header_map_normalize does on Delx Protocol — Agent Recovery & Continuity
AI agents call util_header_map_normalize to permanently remove resources in Delx Protocol — Agent Recovery & Continuity, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
headers | object | Yes | Input field: headers. |
Parameters from the server's own tool schema.
Why util_header_map_normalize is rated Critical
An AI agent that decides to call util_header_map_normalize doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Delx Protocol — Agent Recovery & Continuity is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs util_header_map_normalize safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_header_map_normalize, this is the rule to start with:
util_header_map_normalize is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Protocol — Agent Recovery & Continuity, apply this rule, and every util_header_map_normalize call is checked against it from then on.
Questions about util_header_map_normalize
Lowercase HTTP header keys and drop hop-by-hop headers. It is categorised as a Destructive tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
util_header_map_normalize accepts 1 parameter: headers. Required: headers. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for util_header_map_normalize: 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 Protocol — Agent Recovery & Continuity. Nothing to install.
util_header_map_normalize is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the util_header_map_normalize 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_header_map_normalize. 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_header_map_normalize is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.
This server
Across the catalogue