util_date_diff
Delx first-party micro-utility util_date_diff at $0.001 USDC.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/util-date-diff.md
What util_date_diff does on Delx MCP Server
AI agents call util_date_diff to retrieve information from Delx MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
end | string | Yes | end |
start | string | Yes | start |
Parameters from the server's own tool schema.
Why util_date_diff is rated Low
This is a simple utility function that computes the difference between dates and returns the result. It is read-only: no data is created, modified, or deleted; no code is executed; and no financial transfer occurs (the $0.001 USDC mentioned is the usage fee, not a financial operation performed by the tool).
From the tool's definition Tool name 'util_date_diff' and description indicate a date difference calculation utility. No modification, deletion, execution of external commands, or financial transaction occurs—it performs a pure computational operation that retrieves/calculates a result…
Attacks that exploit this kind of access
The rule that runs util_date_diff safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_date_diff, this is the rule to start with:
util_date_diff is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx MCP Server, apply this rule, and every util_date_diff call is checked against it from then on.
Questions about util_date_diff
Delx first-party micro-utility util_date_diff at $0.001 USDC. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
util_date_diff accepts 2 parameters: end, start. Required: end, start. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for util_date_diff: 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 Server. Nothing to install.
util_date_diff is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the util_date_diff 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_date_diff. 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_date_diff is provided by the Delx MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue