AI agents use create_booking to commit financial operations through Mcp Turo — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Creating a booking on Turo involves agreeing to rental terms and committing to payment for a car rental. This is a financial transaction that charges real money to the user's account. Misuse could result in unauthorized financial commitments, making it Financial category with critical severity.
From the tool's definition 'Create a new car booking/reservation on Turo' and 'Returns booking confirmation details and price breakdown' — this commits a financial obligation (rental payment) on the user's behalf.
Attacks that exploit this kind of access
Create a new car booking/reservation on Turo. Requires the user to be logged in to their Turo account. Returns booking confirmation details and price breakdown. It is categorised as a Financial tool in the Mcp Turo MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Mcp Turo MCP server in PolicyLayer and add a rule for create_booking: 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 Turo. Nothing to install.
create_booking is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the create_booking 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 create_booking. 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.
create_booking is provided by the Mcp Turo MCP server (markswendsen-code/mcp-turo). 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 →