// SCAN REPORT

MCP Uber Server

6 tools. 3 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 11 Jun 2026

3 can modify or destroy data

3 read-only

6 tools total

Community server · catalogue entry verified 11/06/2026

How to control MCP Uber Server ↓

TOOL MAP

What MCP Uber Server exposes to your agents

Read (3) Write / Execute (1) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous MCP Uber Server tools

Financial · Critical uber_request_ride Requesting an Uber ride creates a real financial transaction: the user is charged for the ride. Destructive · High uber_cancel_ride While cancellation is technically a state change, it is functionally irreversible and destructive to the ride transaction. Write · High uber_set_access_token This tool creates or modifies user authentication credentials (access token) that enable subsequent ride-booking operations.

3 of MCP Uber Server's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control MCP Uber Server

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Uber Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "uber_request_ride": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations

{
  "uber_cancel_ride": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "uber_set_access_token": {
    "limits": [
      {
        "counter": "uber_set_access_token_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "uber_get_auth_url": {
    "limits": [
      {
        "counter": "uber_get_auth_url_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register MCP Uber Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MCP UBER →

Free to start. No card required.

FULL CATALOGUE

All 6 MCP Uber Server tools

FINANCIAL 1 tools

Financial uber_request_ride Request an Uber ride

DESTRUCTIVE 1 tools

Destructive uber_cancel_ride Cancel an ongoing ride request

WRITE 1 tools

Write uber_set_access_token Set the access token for a user after OAuth callback

READ 3 tools

Read uber_get_auth_url Get the Uber authorization URL for user to authenticate Read uber_get_price_estimates Get price estimates for a ride between two locations Read uber_get_ride_status Get the current status of a ride request

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about MCP Uber Server

Can an AI agent move money through the MCP Uber Server MCP server? +

Yes. The MCP Uber Server server exposes 1 financial tools including uber_request_ride. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

Can an AI agent delete data through the MCP Uber Server MCP server? +

Yes. The MCP Uber Server server exposes 1 destructive tools including uber_cancel_ride. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through MCP Uber Server? +

The MCP Uber Server server has 1 write tools including uber_set_access_token. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach MCP Uber Server.

How many tools does the MCP Uber Server MCP server expose? +

6 tools across 3 categories: Destructive, Read, Write. 3 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on MCP Uber Server? +

Register the MCP Uber Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every MCP Uber Server tool call.

Deterministic rules across all 6 MCP Uber Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP UBER →

Free to start. No card required.

6 MCP Uber Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.