View past and upcoming Zipcar reservations. Can filter by upcoming or past reservations.
AI agents call get_reservation_history 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.
This tool queries and retrieves reservation data for display purposes only. It has no side effects—it does not create, modify, delete, or execute any actions. The use of 'View' and 'filter' confirms read-only semantics. The blast radius of misuse is minimal: an agent could view reservation history it shouldn't access, but cannot harm systems or cause financial loss through viewing alone.
From the tool's definition Tool name 'get_reservation_history' and description 'View past and upcoming Zipcar reservations. Can filter by upcoming or past reservations' indicate a read-only operation that retrieves historical data without modifying or deleting anything.
Attacks that exploit this kind of access
View past and upcoming Zipcar reservations. Can filter by upcoming or past reservations. 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_reservation_history: 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_reservation_history 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_reservation_history 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_reservation_history. 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_reservation_history 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 →