AI agents call fahrenheit_to_celsius 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 |
|---|---|---|---|
fahrenheit | number | Yes | Temperature in Fahrenheit |
Parameters from the server's own tool schema.
Even though fahrenheit_to_celsius only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Convert Fahrenheit to Celsius. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
fahrenheit_to_celsius accepts 1 parameter: fahrenheit. Required: fahrenheit. 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 fahrenheit_to_celsius: 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.
fahrenheit_to_celsius 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 fahrenheit_to_celsius 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 fahrenheit_to_celsius. 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.
fahrenheit_to_celsius 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.
fahrenheit_to_celsius 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 →