destination_point
Calculate destination point given start, bearing, and distance.
This record as markdown: /tools/io-tinyfn-tinyfn/destination-point.md
What destination_point does on TinyFn
AI agents call destination_point 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 |
|---|---|---|---|
lat | number | Yes | Starting latitude |
lon | number | Yes | Starting longitude |
unit | string | — | Unit: km or mi |
bearing | number | Yes | Bearing in degrees |
distance | number | Yes | Distance to travel |
Parameters from the server's own tool schema.
Why destination_point is rated Low
This tool performs a mathematical/geographical calculation (great-circle navigation) and returns a result. It reads input parameters and computes an output with no external state changes, data writes, or destructive operations.
From the tool's definition 'Calculate destination point given start, bearing, and distance' — pure deterministic computation with no side effects
Attacks that exploit this kind of access
The rule that runs destination_point 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 destination_point, this is the rule to start with:
destination_point 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 destination_point call is checked against it from then on.
Questions about destination_point
Calculate destination point given start, bearing, and distance. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
destination_point accepts 5 parameters: lat, lon, unit, bearing, distance. Required: lat, lon, bearing, distance. 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 destination_point: 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.
destination_point 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 destination_point 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 destination_point. 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.
destination_point 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