number_base
Convert an integer between bases 2–36 (binary, octal, decimal, hex and more), exact for 64-bit values via BigInt. Runs on smart-tools.xyz.
This record as markdown: /tools/io-github-9thshini-smart-tools/number-base.md
What number_base does on SmartTools
AI agents invoke number_base 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 |
|---|---|---|---|
value | string | number | Yes | The integer to convert (may use 0x/0b/0o prefix, spaces or _ as separators) |
locale | string | — | Language for the source_url link (default en) |
to_base | number | string | — | Base to convert to, 2–36 |
from_base | number | string | Yes | Base of the input, 2–36 |
Parameters from the server's own tool schema.
Why number_base is rated High
number_base 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 number_base 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 number_base, this is the rule to start with:
number_base 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 number_base call is checked against it from then on.
Questions about number_base
Convert an integer between bases 2–36 (binary, octal, decimal, hex and more), exact for 64-bit values via BigInt. 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.
number_base accepts 4 parameters: value, locale, to_base, from_base. Required: value, from_base. 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 number_base: 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.
number_base 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 number_base 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 number_base. 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.
number_base 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