AI agents call log to retrieve information from TinyFn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
base | object | — | Base (default: natural log) |
number | number | Yes | Number (must be positive) |
Parameters from the server's own tool schema.
This is a deterministic mathematical function that computes logarithmic values. It performs no I/O, does not modify or delete data, does not execute arbitrary code, and does not interact with external systems. It fits the Read category as a data-retrieval/query operation (though in this case, a computational query rather than a database query).
From the tool's definition Tool name 'log' with description 'Calculate logarithm. Natural log if no base specified.' - a pure mathematical computation with no side effects, data retrieval, or external operations.
Attacks that exploit this kind of access
Calculate logarithm. Natural log if no base specified. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
log accepts 2 parameters: base, 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 log: 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.
log 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 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. 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 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.
log is one line of TinyFn's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →