# uber_get_auth_url

Get the Uber authorization URL for user to authenticate

Agent View of the PolicyLayer registry record for `uber_get_auth_url`. HTML page: https://policylayer.com/tools/199-mcp-mcp-uber/uber-get-auth-url

## Facts

- Tool: `uber_get_auth_url`
- 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: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why uber_get_auth_url is rated Low

This tool only retrieves an authorization URL for authentication purposes. It does not execute code, modify data, delete data, or commit financial obligations. The most severe capability would be if a misused URL could be used for phishing, but the tool itself performs no dangerous action. Classification as Read with low severity is appropriate.

From the tool's own definition: "Tool description states 'Get the Uber authorization URL for user to authenticate' — it retrieves a URL without side effects. This is a read-only query operation that returns an authentication endpoint."

## Use case

AI agents call uber_get_auth_url to retrieve information from MCP Uber Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. 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_get_auth_url": {}
  }
}
```

## Other tools on MCP Uber Server (5)

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