time_converter
Convert a value between time units. Units: µs (Microsecond), ms (Millisecond), s (Second), min (Minute), h (Hour), d (Day), wk (Week), mo (Month), yr (Year). Calculation runs on smart-tools.xyz.
This record as markdown: /tools/io-github-9thshini-smart-tools/time-converter.md
What time_converter does on SmartTools
AI agents invoke time_converter to trigger actions in SmartTools. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | Yes | Target unit id |
from | string | Yes | Source unit id |
value | number | string | Yes | Amount to convert |
locale | string | — | Language for source_url (en, de, es, fr, it, nl, uk) |
Parameters from the server's own tool schema.
Why time_converter is rated High
time_converter triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs time_converter safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For time_converter, this is the rule to start with:
time_converter stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartTools, apply this rule, and every time_converter call is checked against it from then on.
Questions about time_converter
Convert a value between time units. Units: µs (Microsecond), ms (Millisecond), s (Second), min (Minute), h (Hour), d (Day), wk (Week), mo (Month), yr (Year). Calculation runs on smart-tools.xyz. It is categorised as a Execute tool in the SmartTools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
time_converter accepts 4 parameters: to, from, value, locale. Required: to, from, value. The full parameter table on this page comes from the server's own tool schema.
Register the SmartTools MCP server in PolicyLayer and add a rule for time_converter: 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 SmartTools. Nothing to install.
time_converter is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the time_converter 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 time_converter. 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.
time_converter is provided by the SmartTools MCP server (https://smart-tools.xyz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartTools, and thousands of servers like it.
Across the catalogue