log_base
Compute logarithm with any base. Also returns ln, log10, and log2.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/log-base.md
What log_base does on UnClick
AI agents call log_base to retrieve information from UnClick 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 |
|---|---|---|---|
base | number | — | Logarithm base (default 10, must be positive and not 1). |
value | number | Yes | Positive number to compute log of. |
Parameters from the server's own tool schema.
Why log_base is rated Low
This is a straightforward mathematical utility that takes numeric inputs and returns computed logarithmic values. It retrieves/computes and returns data without any side effects on system state, data persistence, external resources, or financial obligations. The low severity reflects that misuse (e.g., requesting very large logarithms) poses minimal harm.
From the tool's definition Tool performs mathematical computation (logarithm calculation) and returns results. The description states 'Compute logarithm with any base.
Attacks that exploit this kind of access
The rule that runs log_base safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For log_base, this is the rule to start with:
log_base 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 UnClick, apply this rule, and every log_base call is checked against it from then on.
Questions about log_base
Compute logarithm with any base. Also returns ln, log10, and log2. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
log_base accepts 2 parameters: base, value. Required: value. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for log_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 UnClick. Nothing to install.
log_base 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 log_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 log_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.
log_base is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue