ip_in_range
Check if an IP address is within a CIDR range.
This record as markdown: /tools/io-tinyfn-tinyfn/ip-in-range.md
What ip_in_range does on TinyFn
AI agents call ip_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 |
|---|---|---|---|
ip | string | Yes | IP address to check |
cidr | string | Yes | CIDR range |
Parameters from the server's own tool schema.
Why ip_in_range is rated Low
This is a deterministic validation tool that performs a comparison operation. It reads input values (an IP address and a CIDR range) and returns a boolean result indicating membership. No data is created, modified, deleted, or executed. It has no side effects and falls squarely into the Read category.
From the tool's definition Tool name 'ip_in_range' and description 'Check if an IP address is within a CIDR range' indicate a query/validation operation that retrieves or checks information without modifying any data or triggering external effects.
Attacks that exploit this kind of access
The rule that runs ip_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 ip_in_range, this is the rule to start with:
ip_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 ip_in_range call is checked against it from then on.
Questions about ip_in_range
Check if an IP address is within a CIDR range. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
ip_in_range accepts 2 parameters: ip, cidr. Required: ip, cidr. 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 ip_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.
ip_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 ip_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 ip_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.
ip_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