Geçmiş yolculukların listesini getirir
AI agents call uber_yolculuk_gecmisi to retrieve information from Uber MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical ride data for the authenticated user. It performs a read-only query operation with no ability to modify, delete, or execute actions. The blast radius is minimal—exposure allows viewing of a user's ride history (potentially sensitive but non-destructive information). This aligns clearly with the Read category (fetch, list, get operations).
From the tool's definition The tool name 'uber_yolculuk_gecmisi' and description 'Geçmiş yolculukların listesini getirir' (retrieves a list of past journeys) indicate a retrieval operation.
Attacks that exploit this kind of access
Geçmiş yolculukların listesini getirir. It is categorised as a Read tool in the Uber MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Uber MCP Server MCP server in PolicyLayer and add a rule for uber_yolculuk_gecmisi: 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 Uber MCP Server. Nothing to install.
uber_yolculuk_gecmisi 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_yolculuk_gecmisi 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_yolculuk_gecmisi. 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_yolculuk_gecmisi is provided by the Uber MCP Server MCP server (skynet-base/uber-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →