# uber_cancel_ride

Cancel an ongoing ride request

Agent View of the PolicyLayer registry record for `uber_cancel_ride`. HTML page: https://policylayer.com/tools/199-mcp-mcp-uber/uber-cancel-ride

## Facts

- Tool: `uber_cancel_ride`
- Server: MCP Uber Server (`199-mcp/mcp-uber`) — https://policylayer.com/tools/199-mcp-mcp-uber.md
- Homepage: https://github.com/199-mcp/mcp-uber
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "uber_cancel_ride",
    "arguments": {}
  }
}
```

## 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 own definition: "The tool 'uber_cancel_ride' with description 'Cancel an ongoing ride request' irreversibly terminates an active ride arrangement."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches MCP Uber Server:

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

## Other tools on MCP Uber Server (5)

- `uber_request_ride` — Financial — https://policylayer.com/tools/199-mcp-mcp-uber/uber-request-ride.md
- `uber_get_auth_url` — Read — https://policylayer.com/tools/199-mcp-mcp-uber/uber-get-auth-url.md
- `uber_get_price_estimates` — Read — https://policylayer.com/tools/199-mcp-mcp-uber/uber-get-price-estimates.md
- `uber_get_ride_status` — Read — https://policylayer.com/tools/199-mcp-mcp-uber/uber-get-ride-status.md
- `uber_set_access_token` — Write — https://policylayer.com/tools/199-mcp-mcp-uber/uber-set-access-token.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=199-mcp-mcp-uber · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/199-mcp-mcp-uber