duration_breakdown
Duration Breakdown Calculator — Elapsed time between two ISO 8601 timestamps broken into weeks/days/hours/minutes/seconds, plus running totals.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/duration-breakdown.md
What duration_breakdown does on Gateway
AI agents call duration_breakdown to retrieve information from Gateway 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 timestamp, ISO 8601 |
start | string | Yes | Start timestamp, ISO 8601 |
Parameters from the server's own tool schema.
Why duration_breakdown is rated Low
This is a pure calculation utility that accepts two timestamps as input and returns formatted time difference data. It performs no state mutations, does not execute arbitrary code or commands, does not delete or overwrite anything, and involves no financial transactions. The tool is read-only in nature—it queries time data and performs arithmetic, returning results without side effects.
From the tool's definition Tool name is 'duration_breakdown' and description states it calculates and breaks down 'elapsed time between two ISO 8601 timestamps' into time units with 'running totals'.
Attacks that exploit this kind of access
The rule that runs duration_breakdown safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For duration_breakdown, this is the rule to start with:
duration_breakdown 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 Gateway, apply this rule, and every duration_breakdown call is checked against it from then on.
Questions about duration_breakdown
Duration Breakdown Calculator — Elapsed time between two ISO 8601 timestamps broken into weeks/days/hours/minutes/seconds, plus running totals. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
duration_breakdown 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 Gateway MCP server in PolicyLayer and add a rule for duration_breakdown: 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 Gateway. Nothing to install.
duration_breakdown 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 duration_breakdown 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 duration_breakdown. 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.
duration_breakdown is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue