is_valid_coordinates
Check if coordinates are valid.
This record as markdown: /tools/io-tinyfn-tinyfn/is-valid-coordinates.md
What is_valid_coordinates does on TinyFn
AI agents call is_valid_coordinates 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 | Latitude to validate |
lon | number | Yes | Longitude to validate |
Parameters from the server's own tool schema.
Why is_valid_coordinates is rated Low
This is a validation tool that performs a read-only check on coordinate data. It retrieves or evaluates information (whether coordinates are valid) with no side effects, no data modification, no code execution, and no destructive operations. It fits the 'Read' category as a pure validation/query function.
From the tool's definition Tool name 'is_valid_coordinates' and description 'Check if coordinates are valid' indicate a validation function that queries/checks data without modifying state or executing external operations.
Attacks that exploit this kind of access
The rule that runs is_valid_coordinates 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 is_valid_coordinates, this is the rule to start with:
is_valid_coordinates 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 is_valid_coordinates call is checked against it from then on.
Questions about is_valid_coordinates
Check if coordinates are valid. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
is_valid_coordinates accepts 2 parameters: lat, lon. Required: lat, lon. 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 is_valid_coordinates: 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.
is_valid_coordinates 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 is_valid_coordinates 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 is_valid_coordinates. 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.
is_valid_coordinates 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