Get detailed information about a specific Zipcar including vehicle type, features, seating, fuel type, and pricing rates.
AI agents call get_car_details to retrieve information from Zipcar MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and returns informational details about a vehicle. It has no side effects on reservations, trip status, or financial transactions. It is purely informational retrieval, making it a Read category tool with low severity.
From the tool's definition Tool description states it 'Get detailed information about a specific Zipcar including vehicle type, features, seating, fuel type, and pricing rates.' This is a retrieval operation with no stated modifications, deletions, or external execution of commands.
Attacks that exploit this kind of access
Get detailed information about a specific Zipcar including vehicle type, features, seating, fuel type, and pricing rates. It is categorised as a Read tool in the Zipcar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zipcar MCP Server MCP server in PolicyLayer and add a rule for get_car_details: 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 Zipcar MCP Server. Nothing to install.
get_car_details 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 get_car_details 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 get_car_details. 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.
get_car_details is provided by the Zipcar MCP Server MCP server (markswendsen-code/mcp-zipcar). 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 →