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

mbta.transit.stops

Find Boston MBTA stops and stations — filter by route ID or by geographic coordinates + radius. Returns stop ID, name, latitude/longitude, municipality, vehicle type, platform info, and wheelchair boarding status. Stop IDs returned here are used as filter inputs for mbta-transit.alerts and mbta-t...

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

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/mbta.transit.stops.md

What mbta.transit.stops does on Apibase

AI agents call mbta.transit.stops 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 stops to return (default 25, max 100)
route string — Filter stops by route ID (e.g. "Red" for Red Line, "1" for Route 1 bus, "CR-Fairmount" for commuter rail). Use mbta-transit.routes to get route IDs.
radius number — Search radius in degrees around lat/lon (approx 0.01° ≈ 1 km). Use with latitude+longitude.
latitude number — Center latitude for proximity search. Must be paired with longitude and radius (e.g. 42.3601 for Boston)
longitude number — Center longitude for proximity search. Must be paired with latitude and radius (e.g. -71.0589 for Boston)
location_type string — Filter by location type: 0=individual stop/platform, 1=station (parent), 2=station entrance/exit

Parameters from the server's own tool schema.

Why mbta.transit.stops is rated Low

Retrieves public transit stop information with no side effects or data modification.

From the tool's definition Find Boston MBTA stops and stations — filter by route ID or geographic coordinates.

Questions about mbta.transit.stops

What does the mbta.transit.stops tool do? +

Find Boston MBTA stops and stations — filter by route ID or by geographic coordinates + radius. Returns stop ID, name, latitude/longitude, municipality, vehicle type, platform info, and wheelchair boarding status. Stop IDs returned here are used as filter inputs for mbta-transit.alerts and mbta-transit.predictions. Use location_type=1 to return only major stations (parent stops); location_type=0 for individual platforms. Example: route="Red" returns all 22 Red Line stops from Alewife to Braintree/Ashmont. MassDOT Open Data License, no upstream cost. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does mbta.transit.stops accept? +

mbta.transit.stops accepts 6 parameters: limit, route, radius, latitude, longitude, location_type. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on mbta.transit.stops? +

Register the Apibase MCP server in PolicyLayer and add a rule for mbta.transit.stops: 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 mbta.transit.stops? +

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

Can I rate-limit mbta.transit.stops? +

Yes. Add a rate_limit block to the mbta.transit.stops 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 mbta.transit.stops completely? +

Set action: deny in the PolicyLayer policy for mbta.transit.stops. 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 mbta.transit.stops? +

mbta.transit.stops 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.