util_content_type_parse
Content Type Parse splits a Content-Type value into media type and parameters from bounded caller-supplied values without an external provider. Call Content Type Parse before accepting, caching, redirecting, or retrying a caller-supplied web response. Returns normalized web evidence, the computed...
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/util-content-type-parse.md
What util_content_type_parse does on Delx Mcp A2a
AI agents use util_content_type_parse to create or update resources in Delx Mcp A2a, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx Mcp A2a environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
header | string | Yes | Header supplied to Content Type Parse; used only for this bounded calculation and processed in memory without retention. |
Parameters from the server's own tool schema.
Why util_content_type_parse is rated Medium
An AI agent can call util_content_type_parse faster than any human can review: one bad instruction and it creates or modifies resources in Delx Mcp A2a by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs util_content_type_parse safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_content_type_parse, this is the rule to start with:
util_content_type_parse 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Mcp A2a, apply this rule, and every util_content_type_parse call is checked against it from then on.
Questions about util_content_type_parse
Content Type Parse splits a Content-Type value into media type and parameters from bounded caller-supplied values without an external provider. Call Content Type Parse 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 Parse 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 Mcp A2a MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
util_content_type_parse accepts 1 parameter: header. Required: header. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for util_content_type_parse: 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 Mcp A2a. Nothing to install.
util_content_type_parse is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the util_content_type_parse 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_content_type_parse. 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_content_type_parse is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue