Get price estimates for a ride between two locations
AI agents call uber_get_price_estimates to retrieve information from MCP Uber Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pricing information for hypothetical rides without creating, modifying, deleting, or executing any operations. It does not commit any financial obligations or perform any irreversible actions. While the server as a whole includes financial tools (like uber_request_ride which commits a ride booking), this specific tool only queries and returns data.
From the tool's definition Tool name 'uber_get_price_estimates' and description 'Get price estimates for a ride between two locations' indicate data retrieval with no side effects. The verb 'Get' and the word 'estimates' confirm this is a query operation.
Documented attack patterns abuse exactly the kind of access uber_get_price_estimates gives an agent:
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_get_price_estimates:
{
"version": "1",
"default": "deny",
"tools": {
"uber_get_price_estimates": {}
}
} uber_get_price_estimates is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get price estimates for a ride between two locations. It is categorised as a Read tool in the MCP Uber Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Uber Server MCP server in PolicyLayer and add a rule for uber_get_price_estimates: 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.
uber_get_price_estimates is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the uber_get_price_estimates 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.
Set action: deny in the PolicyLayer policy for uber_get_price_estimates. 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.
uber_get_price_estimates 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.
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.