AI agents call base_convert to retrieve information from Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
from | string | — | Source base (default: dec) |
value | string | Yes | Number to convert |
Parameters from the server's own tool schema.
This tool performs a pure mathematical conversion between number bases. It reads input and returns output with no side effects, no data persistence, and no external operations. Misuse potential is negligible.
From the tool's definition Convert numbers between decimal, binary, octal, hexadecimal
Attacks that exploit this kind of access
Convert numbers between decimal, binary, octal, hexadecimal. It is categorised as a Read tool in the Tools MCP Server, which means it retrieves data without modifying state.
base_convert accepts 2 parameters: from, value. Required: value. The full parameter table on this page comes from the server's own tool schema.
Register the Tools MCP server in PolicyLayer and add a rule for base_convert: 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 Tools. Nothing to install.
base_convert 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 base_convert 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 base_convert. 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.
base_convert is provided by the Tools MCP server (https://www.jiebang.site/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →