private_ip_ranges
Get RFC 1918 private IP address ranges.
This record as markdown: /tools/io-tinyfn-tinyfn/private-ip-ranges.md
What private_ip_ranges does on TinyFn
AI agents call private_ip_ranges 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.
Why private_ip_ranges is rated Low
This tool retrieves informational data about private IP address ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) with no side effects, modifications, deletions, or external operations. It is a simple lookup/query operation. Severity is low because misuse cannot directly harm systems—at worst, an agent could use this information for reconnaissance planning, but the data is publicly documented and widely known.
From the tool's definition Tool name 'private_ip_ranges' and description 'Get RFC 1918 private IP address ranges' indicate a retrieval operation that returns static reference data about IP address ranges defined in RFC 1918.
Attacks that exploit this kind of access
The rule that runs private_ip_ranges 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 private_ip_ranges, this is the rule to start with:
private_ip_ranges 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 private_ip_ranges call is checked against it from then on.
Questions about private_ip_ranges
Get RFC 1918 private IP address ranges. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
Register the TinyFn MCP server in PolicyLayer and add a rule for private_ip_ranges: 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.
private_ip_ranges 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 private_ip_ranges 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 private_ip_ranges. 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.
private_ip_ranges 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