Critical Risk →

uber_request_ride

Request an Uber ride

How to control uber_request_ride ↓

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.

Critical Risk

Why uber_request_ride needs a policy

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

Documented attack patterns abuse exactly the kind of access uber_request_ride gives an agent:

How to control uber_request_ride

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

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

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

  1. Create a free account and register MCP Uber Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
GATE THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

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.

Enforce policy on every MCP Uber Server tool call.

Start from MCP Uber Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.