This record as markdown: /tools/io-tinyfn-tinyfn/in-range.md
What in_range does on TinyFn
AI agents call in_range 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 |
|---|---|---|---|
value | number | Yes | Value to check |
max_val | number | Yes | Maximum value |
min_val | number | Yes | Minimum value |
Parameters from the server's own tool schema.
Why in_range is rated Low
This is a deterministic validation function that tests whether a value falls within specified bounds. It performs no writes, deletions, code execution, or financial operations. It is a pure read/check operation consistent with the server's purpose of providing utility functions for AI agents.
From the tool's definition Tool name 'in_range' and description 'Check if a value is within a range' indicate a query/validation operation that retrieves or checks data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs in_range 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 in_range, this is the rule to start with:
in_range 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 in_range call is checked against it from then on.
Questions about in_range
Check if a value is within a range. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
in_range accepts 3 parameters: value, max_val, min_val. Required: value, max_val, min_val. 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 in_range: 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.
in_range 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 in_range 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 in_range. 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.
in_range 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