# uber_request_ride

Request an Uber ride

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

## Facts

- Tool: `uber_request_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: Financial (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Approval-gated

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

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

## Why uber_request_ride is rated Critical

Requesting an Uber ride creates a real financial transaction: the user is charged for the ride. This falls squarely in the Financial category as it commits financial obligations. The blast radius is critical because an AI agent could book rides without explicit user confirmation, leading to unwanted charges and potential fraud.

From the tool's own definition: "'Request an Uber ride' — directly initiates a paid ride booking, committing a financial obligation on the user's account"

## Use case

AI agents use uber_request_ride to commit financial operations through MCP Uber Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "uber_request_ride": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}
```

## Other tools on MCP Uber Server (5)

- `uber_cancel_ride` — Destructive — https://policylayer.com/tools/199-mcp-mcp-uber/uber-cancel-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