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

util_content_type_match

Content Type Match checks a concrete Content-Type against an expected media range from bounded caller-supplied values without an external provider. Call Content Type Match before accepting, caching, redirecting, or retrying a caller-supplied web response. Returns normalized web evidence, the comp...

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-content-type-match.md

What util_content_type_match does on Delx Protocol — Agent Recovery & Continuity

AI agents use util_content_type_match 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.

ParameterTypeRequiredDescription
actual string Yes Actual supplied to Content Type Match; used only for this bounded calculation and processed in memory without retention.
expected string Yes Expected supplied to Content Type Match; used only for this bounded calculation and processed in memory without retention.

Parameters from the server's own tool schema.

Why util_content_type_match is rated Medium

An AI agent can call util_content_type_match 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.

Questions about util_content_type_match

What does the util_content_type_match tool do? +

Content Type Match checks a concrete Content-Type against an expected media range from bounded caller-supplied values without an external provider. Call Content Type Match 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 Content Type Match 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_content_type_match accept? +

util_content_type_match accepts 2 parameters: actual, expected. Required: actual, expected. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on util_content_type_match? +

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

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

Can I rate-limit util_content_type_match? +

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

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

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