AI agents call ip_in_network 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 |
|---|---|---|---|
ip | string | Yes | IP address to check |
network | string | Yes | Network in CIDR notation |
Parameters from the server's own tool schema.
This is a deterministic validation/query tool that reads input parameters (an IP address and a network) and returns a boolean result. It performs no side effects, creates no data, executes no code, and triggers no external operations. It aligns with the Read category as a simple lookup or validation function with no blast radius if misused by an AI agent.
From the tool's definition Tool name 'ip_in_network' and description 'Check if an IP address is within a network' indicate a query operation that validates/checks membership without modifying data or triggering external operations.
Attacks that exploit this kind of access
Check if an IP address is within a network. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
ip_in_network accepts 2 parameters: ip, network. Required: ip, network. 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_network: 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_network 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_network 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_network. 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_network 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.
ip_in_network 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 →