mbta.transit.routes
List Boston MBTA transit routes by type — subway (Red/Orange/Blue/Green lines), commuter rail (Providence, Fairmount, etc.), bus, and ferry. Returns route ID, long name, type label, direction names and destinations, fare class, and brand color. Route IDs returned here are used as filter inputs fo...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/mbta.transit.routes.md
What mbta.transit.routes does on Apibase
AI agents call mbta.transit.routes 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 |
|---|---|---|---|
sort | string | — | Sort order: "sort_order" (default MBTA order), "long_name" alphabetical, prefix "-" for descending |
type | string | — | Filter by route type: 0=Light Rail, 1=Heavy Rail/Subway, 2=Commuter Rail, 3=Bus, 4=Ferry. Omit for all types. |
limit | integer | — | Maximum number of routes to return (default 50, max 100) |
Parameters from the server's own tool schema.
Why mbta.transit.routes is rated Low
Tool retrieves public transit route information with no side effects, modifications, or external operations.
From the tool's definition List Boston MBTA transit routes by type — returns route ID, long name, type label, direction names and destinations.
Attacks that exploit this kind of access
The rule that runs mbta.transit.routes 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 mbta.transit.routes, this is the rule to start with:
mbta.transit.routes 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 mbta.transit.routes call is checked against it from then on.
Questions about mbta.transit.routes
List Boston MBTA transit routes by type — subway (Red/Orange/Blue/Green lines), commuter rail (Providence, Fairmount, etc.), bus, and ferry. Returns route ID, long name, type label, direction names and destinations, fare class, and brand color. Route IDs returned here are used as filter inputs for mbta-transit.stops, mbta-transit.alerts, and mbta-transit.predictions. Filter by type: 0=Light Rail, 1=Heavy Rail/Subway, 2=Commuter Rail, 3=Bus, 4=Ferry. 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.
mbta.transit.routes accepts 3 parameters: sort, type, limit. 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 mbta.transit.routes: 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.
mbta.transit.routes 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 mbta.transit.routes 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 mbta.transit.routes. 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.
mbta.transit.routes 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