This record as markdown: /tools/io-tinyfn-tinyfn/log2.md
What log2 does on TinyFn
AI agents call log2 to retrieve information from TinyFn 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 |
|---|---|---|---|
number | number | Yes | Number (must be positive) |
Parameters from the server's own tool schema.
Why log2 is rated Low
This is a deterministic mathematical function that takes input and returns a computed result. It performs no I/O, does not modify any data, does not execute external commands, and has no capability to cause harm even if misused by an AI agent. It fits the Read category as a data-independent computation, though it could also be considered 'Other' since it has no data retrieval aspect.
From the tool's definition Tool name 'log2' and description 'Calculate base-2 logarithm' indicate a pure mathematical computation with no side effects, data retrieval, modification, or external operations.
Attacks that exploit this kind of access
The rule that runs log2 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TinyFn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For log2, this is the rule to start with:
log2 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 TinyFn, apply this rule, and every log2 call is checked against it from then on.
Questions about log2
Calculate base-2 logarithm. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
log2 accepts 1 parameter: number. Required: number. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for log2: 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 TinyFn. Nothing to install.
log2 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 log2 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 log2. 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.
log2 is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TinyFn, and thousands of servers like it.
This server
Across the catalogue