calculate_midpoint
Calculate geographic midpoint between two coordinates.
This record as markdown: /tools/io-tinyfn-tinyfn/calculate-midpoint.md
What calculate_midpoint does on TinyFn
AI agents call calculate_midpoint 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 |
|---|---|---|---|
lat1 | number | Yes | Latitude of point 1 |
lat2 | number | Yes | Latitude of point 2 |
lon1 | number | Yes | Longitude of point 1 |
lon2 | number | Yes | Longitude of point 2 |
Parameters from the server's own tool schema.
Why calculate_midpoint is rated Low
This is a deterministic mathematical calculation tool that takes two geographic coordinates as input and returns a computed midpoint. It has no side effects, does not access external systems, does not modify state, and does not execute arbitrary code. It fits the Read category as a data retrieval/computation function, though it's closer to 'Other' in that it's purely computational with no actual data retrieval.
From the tool's definition Tool name 'calculate_midpoint' and description 'Calculate geographic midpoint between two coordinates' indicate a pure computation that retrieves no data, modifies nothing, executes no external operations, and produces only a mathematical result based on…
Attacks that exploit this kind of access
The rule that runs calculate_midpoint 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 calculate_midpoint, this is the rule to start with:
calculate_midpoint 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 calculate_midpoint call is checked against it from then on.
Questions about calculate_midpoint
Calculate geographic midpoint between two coordinates. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
calculate_midpoint accepts 4 parameters: lat1, lat2, lon1, lon2. Required: lat1, lat2, lon1, lon2. 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 calculate_midpoint: 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.
calculate_midpoint 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 calculate_midpoint 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 calculate_midpoint. 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.
calculate_midpoint 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