New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

util_expires_header_validate

Expires Header Validate compares Date and Expires timestamps for an explicit cache lifetime from bounded caller-supplied values without an external provider. Call Expires Header Validate before accepting, caching, redirecting, or retrying a caller-supplied web response. Returns normalized web evi...

SERVERDelx Protocol — Agent Recovery & Continuity SOURCEhttps://api.delx.ai/v1/mcp?src=registry
Low RISK CLASS
Category Read
Parameters 22 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What util_expires_header_validate does on Delx Protocol — Agent Recovery & Continuity

AI agents call util_expires_header_validate to retrieve information from Delx Protocol — Agent Recovery & Continuity without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
date_epoch integer Yes Date Epoch supplied to Expires Header Validate; used only for this bounded calculation and processed in memory without retention.
expires_epoch integer Yes Expires Epoch supplied to Expires Header Validate; used only for this bounded calculation and processed in memory without retention.

Parameters from the server's own tool schema.

Why util_expires_header_validate is rated Low

Even though util_expires_header_validate only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about util_expires_header_validate

What does the util_expires_header_validate tool do? +

Expires Header Validate compares Date and Expires timestamps for an explicit cache lifetime from bounded caller-supplied values without an external provider. Call Expires Header Validate 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 Expires Header Validate 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 Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.

What parameters does util_expires_header_validate accept? +

util_expires_header_validate accepts 2 parameters: date_epoch, expires_epoch. Required: date_epoch, expires_epoch. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on util_expires_header_validate? +

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

util_expires_header_validate is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit util_expires_header_validate? +

Yes. Add a rate_limit block to the util_expires_header_validate 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_expires_header_validate completely? +

Set action: deny in the PolicyLayer policy for util_expires_header_validate. 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_expires_header_validate? +

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Delx Protocol — Agent Recovery & Continuity's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.