New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

tfl.transit.bike_points

Get real-time availability of Santander Cycles (formerly Boris Bikes) at all 800+ docking stations across London. Returns for each station: name, coordinates, number of available bikes (standard + e-bikes), empty docks, and total dock capacity. Optionally filter by station name keyword (e.g. Wate...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 20 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/tfl.transit.bike-points.md

What tfl.transit.bike_points does on Apibase

AI agents call tfl.transit.bike_points 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.

ParameterTypeRequiredDescription
limit integer — Maximum number of docking stations to return (1–200). Defaults to 50. Use with query to narrow results to a specific area.
query string — Search by station name or location keyword to filter bike docking points (e.g. Waterloo, Soho, Hyde Park, Paddington). Returns all 799+ stations when omitted.

Parameters from the server's own tool schema.

Why tfl.transit.bike_points is rated Low

Retrieves public transit data with no side effects, modifications, or financial impact.

From the tool's definition Get real-time availability of Santander Cycles at docking stations. Returns name, coordinates, bikes, docks, capacity.

Risk signalsBulk/mass operation — affects multiple targets

Questions about tfl.transit.bike_points

What does the tfl.transit.bike_points tool do? +

Get real-time availability of Santander Cycles (formerly Boris Bikes) at all 800+ docking stations across London. Returns for each station: name, coordinates, number of available bikes (standard + e-bikes), empty docks, and total dock capacity. Optionally filter by station name keyword (e.g. Waterloo, Hyde Park, Soho, Paddington). Availability updates approximately every 2 minutes from the TfL live feed. Useful for cycle hire planning, last-mile commuting, and real-time docking station capacity monitoring. Source: TfL Unified API — api.tfl.gov.uk. No auth required, TfL Open Data CC-BY. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does tfl.transit.bike_points accept? +

tfl.transit.bike_points accepts 2 parameters: limit, query. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on tfl.transit.bike_points? +

Register the Apibase MCP server in PolicyLayer and add a rule for tfl.transit.bike_points: 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.

What risk level is tfl.transit.bike_points? +

tfl.transit.bike_points is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit tfl.transit.bike_points? +

Yes. Add a rate_limit block to the tfl.transit.bike_points 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.

How do I block tfl.transit.bike_points completely? +

Set action: deny in the PolicyLayer policy for tfl.transit.bike_points. 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.

What MCP server provides tfl.transit.bike_points? +

tfl.transit.bike_points 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.