Cancel a pending or active Lyft ride.
AI agents call cancel_ride to permanently remove resources in Mcp Lyft — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancellation of a ride is irreversible and can incur financial penalties depending on the ride status and Lyft's policy. This qualifies as Destructive because the action cannot be undone and has lasting consequences. While Financial might apply due to potential fees, the primary action is the irreversible termination of a service, making Destructive the most accurate primary category.
From the tool's definition Tool name is 'cancel_ride' and description states it can 'Cancel a pending or active Lyft ride.' Cancellation is an irreversible action that terminates a ride request or active trip and may trigger financial consequences (cancellation fees).
Attacks that exploit this kind of access
Cancel a pending or active Lyft ride. It is categorised as a Destructive tool in the Mcp Lyft MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Lyft MCP server in PolicyLayer and add a rule for cancel_ride: 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 Mcp Lyft. Nothing to install.
cancel_ride is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_ride 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 cancel_ride. 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.
cancel_ride is provided by the Mcp Lyft MCP server (markswendsen-code/mcp-lyft). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →