util_location_header_resolve

SERVERDelx Protocol — Agent Recovery & Continuity SOURCEhttps://api.delx.ai/v1/mcp?src=registry

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-davidmosiah-delx-protocol/util-location-header-resolve.md

WHAT IT DOES

What util_location_header_resolve does on Delx Protocol — Agent Recovery & Continuity

AI agents use util_location_header_resolve to create or update resources in Delx Protocol — Agent Recovery & Continuity, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx Protocol — Agent Recovery & Continuity environment.

Parameter	Type	Required	Description
`base_url`	string	Yes	Base URL supplied to Location Header Resolve; used only for this bounded calculation and processed in memory without retention.
`location`	string	Yes	Location supplied to Location Header Resolve; used only for this bounded calculation and processed in memory without retention.

Parameters from the server's own tool schema.

RISK

Why util_location_header_resolve is rated Medium

An AI agent can call util_location_header_resolve faster than any human can review: one bad instruction and it creates or modifies resources in Delx Protocol — Agent Recovery & Continuity by the hundred, each call as confident as the last.

Risk signalsAccepts URL/endpoint input (base_url)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs util_location_header_resolve 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_location_header_resolve, this is the rule to start with:

util_location_header_resolve Rate-limited

util_location_header_resolve stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "util_location_header_resolve": {
      "limits": [
        {
          "counter": "util_location_header_resolve_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Delx Protocol — Agent Recovery & Continuity, apply this rule, and every util_location_header_resolve call is checked against it from then on.

FAQ

Questions about util_location_header_resolve

What does the util_location_header_resolve tool do? +

Location Header Resolve resolves a relative Location value against a caller-supplied base URL from bounded caller-supplied values without an external provider. Call Location Header Resolve before accepting, caching, redirecting, or retrying a caller-supplied web response. Returns normalized web evidence, the computed finding, and an explicit pass or advisory status for Location Header Resolve as versioned deterministic JSON. Limitation: Evaluates only caller-supplied metadata; it performs no DNS lookup, HTTP request, web search, credential use, or persistent storage. It is categorised as a Write tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does util_location_header_resolve accept? +

util_location_header_resolve accepts 2 parameters: base_url, location. Required: base_url, location. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on util_location_header_resolve? +

Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for util_location_header_resolve: 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.

What risk level is util_location_header_resolve? +

util_location_header_resolve is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit util_location_header_resolve? +

Yes. Add a rate_limit block to the util_location_header_resolve 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.

How do I block util_location_header_resolve completely? +

Set action: deny in the PolicyLayer policy for util_location_header_resolve. 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.

What MCP server provides util_location_header_resolve? +

util_location_header_resolve 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.

KEEP EXPLORING

More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.

This server

All 1076 Delx Protocol — Agent Recovery & Continuity tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →