Search for available Zipcars near a location for a given time period. Returns a list of available vehicles with rates and locations.
AI agents call search_cars 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.
search_cars performs a read-only search operation that queries available vehicle inventory and returns informational results. It does not create, modify, delete, or execute any actions—it merely retrieves and presents data about available cars. This is a classic Read category tool with minimal risk.
From the tool's definition Tool description states it 'Search for available Zipcars' and 'Returns a list of available vehicles with rates and locations.' These are query/retrieval operations with no side effects.
Attacks that exploit this kind of access
Search for available Zipcars near a location for a given time period. Returns a list of available vehicles with rates and locations. 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 search_cars: 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.
search_cars 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 search_cars 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 search_cars. 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.
search_cars 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 →