transitpulse
TransitPulse: TransitPulse — global public transit intelligence: route reliability, delay prediction, multi-modal trip planning, city transit scores, and commute optimization for 500+ cities worldwide. NEW: rail/coach/ferry/cruise compensation recovery engine — UK Delay Repay, EU Rail 2021/782, f...
This record as markdown: /tools/com-theaslangroupllc-pulse-pulsenetwork/transitpulse.md
What transitpulse does on Pulsenetwork
AI agents call transitpulse to retrieve information from Pulsenetwork 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 |
|---|---|---|---|
to | string | — | Destination neighborhood or address |
city | string | — | City name (e.g. London, NYC, Tokyo; default: London) |
from | string | — | Origin neighborhood or address |
lang | string | — | Letter language (default English) |
line | string | — | Specific line or route to focus on |
mode | string | — | Transport mode |
time | string | — | Time of travel (e.g. 9am, rush hour) |
cause | string | — | Disruption cause (default unknown — exemption burden is the operator's) |
route | string | — | Line or route name (e.g. L train, Northern line) |
action | string | Yes | Which endpoint to call. Options: status | city | route | commute | airport | agencies | delays | delays-history | trip | multimodal | compare | carfree | visito |
cities | string | — | Alternative: comma-separated pair (e.g. NYC,London) |
city_a | string | — | First city |
Parameters from the server's own tool schema.
Why transitpulse is rated Low
TransitPulse retrieves transit data and generates planning recommendations without modifying systems or triggering external actions.
From the tool's definition route reliability, delay prediction, multi-modal trip planning, city transit scores, commute optimization, live service status.
Risk signalsHigh parameter count (37 properties)
Attacks that exploit this kind of access
The rule that runs transitpulse safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pulsenetwork, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transitpulse, this is the rule to start with:
transitpulse 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 Pulsenetwork, apply this rule, and every transitpulse call is checked against it from then on.
Questions about transitpulse
TransitPulse: TransitPulse — global public transit intelligence: route reliability, delay prediction, multi-modal trip planning, city transit scores, and commute optimization for 500+ cities worldwide. NEW: rail/coach/ferry/cruise compensation recovery engine — UK Delay Repay, EU Rail 2021/782, ferry 1177/2010, coach 181/2011, US FMC cruise refunds, Athens Convention baggage — deterministic eligibility ($0.10) + citation-locked claim letters ($2.00). Coverage: Global Endpoints: • status ($0.05): Live Service Status • city ($0.08): City Transit Intelligence Brief • route ($0.08): Route Reliability Analysis • commute ($0.10): Commute Quality Analysis • airport ($0.08): Airport Transit Guide • agencies ($0.05): Transit Agencies Lookup • delays ($0.05): Current Transit Delays • delays-history ($0.08): Historical Delay Patterns • trip ($0.05): Transit Trip Planning • multimodal ($0.10): Multi-Modal Journey Planning • compare ($0.12): City-to-City Transit Comparison • carfree ($0.12): Car-Free Livability Score • visitor ($0.08): First-Timer Visitor Guide • coverage ($0.10): Transit Coverage Analysis • check ($0.05): Rail/Coach/Ferry/Cruise Compensation Eligibility Check • letter ($2.00): Citation-Locked Transit Compensation Claim Letter. It is categorised as a Read tool in the Pulsenetwork MCP Server, which means it retrieves data without modifying state.
transitpulse accepts 12 parameters: to, city, from, lang, line, mode, time, cause, route, action, cities, city_a. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Pulsenetwork MCP server in PolicyLayer and add a rule for transitpulse: 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 Pulsenetwork. Nothing to install.
transitpulse 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 transitpulse 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 transitpulse. 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.
transitpulse is provided by the Pulsenetwork MCP server (https://pulse.theaslangroupllc.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pulsenetwork, and thousands of servers like it.
This server
Across the catalogue