gov.sg.taxi_availability
Live taxi positions across Singapore aggregated to a 5km grid — returns the top 30 zones by taxi count and the timestamp of the snapshot. LTA, SG Open Data Licence v1.0
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gov.sg.taxi-availability.md
What gov.sg.taxi_availability does on Apibase
AI agents call gov.sg.taxi_availability to retrieve information from Apibase 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 |
|---|---|---|---|
refresh | boolean | — | Set to true to bypass cache and re-fetch the latest snapshot. |
Parameters from the server's own tool schema.
Why gov.sg.taxi_availability is rated Low
Queries live public taxi availability data with no side effects or data modification capability.
From the tool's definition Live taxi positions aggregated to 5km grid, returns top 30 zones, read-only snapshot.
Attacks that exploit this kind of access
The rule that runs gov.sg.taxi_availability safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gov.sg.taxi_availability, this is the rule to start with:
gov.sg.taxi_availability 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 Apibase, apply this rule, and every gov.sg.taxi_availability call is checked against it from then on.
Questions about gov.sg.taxi_availability
Live taxi positions across Singapore aggregated to a 5km grid — returns the top 30 zones by taxi count and the timestamp of the snapshot. LTA, SG Open Data Licence v1.0. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
gov.sg.taxi_availability accepts 1 parameter: refresh. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for gov.sg.taxi_availability: 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 Apibase. Nothing to install.
gov.sg.taxi_availability 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 gov.sg.taxi_availability 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 gov.sg.taxi_availability. 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.
gov.sg.taxi_availability is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue