calculate_bearing
Calculate bearing (direction) between two coordinates.
This record as markdown: /tools/io-tinyfn-tinyfn/calculate-bearing.md
What calculate_bearing does on TinyFn
AI agents call calculate_bearing 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 start point |
lat2 | number | Yes | Latitude of end point |
lon1 | number | Yes | Longitude of start point |
lon2 | number | Yes | Longitude of end point |
Parameters from the server's own tool schema.
Why calculate_bearing is rated Low
This is a pure computational/query operation that takes geographic coordinates as input and returns a calculated bearing value. It has no side effects, does not modify any data, does not execute external commands, and does not move money. It falls squarely into the Read category as a mathematical/analytical function.
From the tool's definition Tool 'calculate_bearing' performs a calculation of directional bearing between two geographic coordinates. It retrieves/computes output based on input parameters with no data modification, deletion, or external operation execution.
Attacks that exploit this kind of access
The rule that runs calculate_bearing 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_bearing, this is the rule to start with:
calculate_bearing 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_bearing call is checked against it from then on.
Questions about calculate_bearing
Calculate bearing (direction) between two coordinates. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
calculate_bearing 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_bearing: 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_bearing 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_bearing 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_bearing. 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_bearing 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