Yeni bir Uber yolculuğu talep eder
AI agents invoke uber_arac_cagir to trigger actions in Uber MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Requesting a ride initiates an external operation with real-world consequences (a driver is dispatched, a trip begins). While it has financial implications, it is primarily an execution of an external service action rather than a direct financial transaction. However, it could incur financial obligations, making it borderline Financial/Execute.
From the tool's definition 'Yeni bir Uber yolculuğu talep eder' (Requests a new Uber ride) — triggers an external real-world operation by dispatching a driver through the Uber API
Attacks that exploit this kind of access
Yeni bir Uber yolculuğu talep eder. It is categorised as a Execute tool in the Uber MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Uber MCP Server MCP server in PolicyLayer and add a rule for uber_arac_cagir: 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_arac_cagir is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the uber_arac_cagir 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_arac_cagir. 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_arac_cagir 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 →