uber_request_ride

Request an Uber ride

SERVERMCP Uber Server SOURCE199-mcp/mcp-uber

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What uber_request_ride does on MCP Uber Server

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.

RISK

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 definition 'Request an Uber ride' — directly initiates a paid ride booking, committing a financial obligation on the user's account

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs uber_request_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_request_ride, this is the rule to start with:

uber_request_ride Approval-gated

Any call to uber_request_ride is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

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

GATE 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_request_ride call is checked against it from then on.

FAQ

Questions about uber_request_ride

What does the uber_request_ride tool do? +

Request an Uber ride. It is categorised as a Financial tool in the MCP Uber Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on uber_request_ride? +

Register the MCP Uber Server MCP server in PolicyLayer and add a rule for uber_request_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_request_ride? +

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

Can I rate-limit uber_request_ride? +

Yes. Add a rate_limit block to the uber_request_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_request_ride completely? +

Set action: deny in the PolicyLayer policy for uber_request_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_request_ride? +

uber_request_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

request_virtual_card on Pop Pay → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →