uber_cancel_ride

Cancel an ongoing ride request

SERVERMCP Uber Server SOURCE199-mcp/mcp-uber

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/199-mcp-mcp-uber/uber-cancel-ride.md

WHAT IT DOES

What uber_cancel_ride does on MCP Uber Server

AI agents call uber_cancel_ride to permanently remove resources in MCP Uber Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why uber_cancel_ride is rated Critical

While cancellation is technically a state change, it is functionally irreversible and destructive to the ride transaction. Once cancelled, the ride cannot be resumed; a new request must be made. This qualifies as Destructive rather than Write because the action cannot be rolled back and has binding consequences. Severity is high because misuse could cancel legitimate rides, strand users, and incur unexpected fees.

From the tool's definition The tool 'uber_cancel_ride' with description 'Cancel an ongoing ride request' irreversibly terminates an active ride arrangement.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs uber_cancel_ride safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Uber Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For uber_cancel_ride, this is the rule to start with:

uber_cancel_ride Hidden

uber_cancel_ride is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "uber_cancel_ride"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Uber Server, apply this rule, and every uber_cancel_ride call is checked against it from then on.

FAQ

Questions about uber_cancel_ride

What does the uber_cancel_ride tool do? +

Cancel an ongoing ride request. It is categorised as a Destructive tool in the MCP Uber Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on uber_cancel_ride? +

Register the MCP Uber Server MCP server in PolicyLayer and add a rule for uber_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 Uber Server. Nothing to install.

What risk level is uber_cancel_ride? +

uber_cancel_ride is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit uber_cancel_ride? +

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

How do I block uber_cancel_ride completely? +

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

What MCP server provides uber_cancel_ride? +

uber_cancel_ride is provided by the MCP Uber Server MCP server (199-mcp/mcp-uber). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Uber Server, and thousands of servers like it.

This server

All 6 MCP Uber Server tools → Critical-risk tools on this server →

Across the catalogue

sms_cancel_scheduled on Twilio SMS MCP Server →cancel_all_orders on Lighter MCP → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →