Get listing history for a vehicle by VIN.
AI agents call get_car_history to retrieve information from MarketCheck MCP Apps without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries historical listing data for a vehicle identified by VIN. It is purely informational—no data is created, modified, deleted, or overwritten. No code execution or financial transactions occur. The blast radius of misuse is minimal since the information returned is historical market data. This clearly falls under the Read category.
From the tool's definition Tool name is 'get_car_history' and description states 'Get listing history for a vehicle by VIN.' The verb 'Get' and the passive retrieval of historical data indicate a read-only operation with no modifications or side effects.
Attacks that exploit this kind of access
Get listing history for a vehicle by VIN. It is categorised as a Read tool in the MarketCheck MCP Apps MCP Server, which means it retrieves data without modifying state.
Register the MarketCheck MCP Apps MCP server in PolicyLayer and add a rule for get_car_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 MarketCheck MCP Apps. Nothing to install.
get_car_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_car_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_car_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_car_history is provided by the MarketCheck MCP Apps MCP server (marketcheckhub/marketcheck-api-mcp-apps). 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 →