AI agents call get_locations to retrieve information from Mcp Hertz without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to retrieve publicly available information about Hertz rental locations. It does not create, modify, delete, or execute actions—merely fetches and returns location data. The blast radius of misuse is minimal; an AI agent could at worst retrieve location information repeatedly or excessively, but cannot cause financial harm, delete data, or trigger destructive actions.
From the tool's definition Tool name 'get_locations' and description 'Search for Hertz rental locations' indicates a retrieval operation. Returns only location details (address, hours, contact information) with no side effects or modifications to data.
Attacks that exploit this kind of access
Search for Hertz rental locations near a city, airport, or coordinates. Returns location details including address, hours, and contact information. It is categorised as a Read tool in the Mcp Hertz MCP Server, which means it retrieves data without modifying state.
Register the Mcp Hertz MCP server in PolicyLayer and add a rule for get_locations: 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 Hertz. Nothing to install.
get_locations 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_locations 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_locations. 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_locations is provided by the Mcp Hertz MCP server (markswendsen-code/mcp-hertz). 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 →