vehicle.carmarket.listing
Get full details for a specific car listing by ID — VIN, price, MSRP, mileage, full build specs (engine, transmission, drivetrain, fuel type), dealer contact, Carfax 1-owner status, days on market, photos. Get listing IDs from carmarket.search (MarketCheck)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/vehicle.carmarket.listing.md
What vehicle.carmarket.listing does on Apibase
AI agents call vehicle.carmarket.listing to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | MarketCheck listing ID (e.g. "3TMCZ5AN5PM564843-883937ce-f335"). Get IDs from carmarket.search results |
Parameters from the server's own tool schema.
Why vehicle.carmarket.listing is rated Low
Retrieves read-only vehicle listing data; no side effects or data modification.
From the tool's definition Get full details for a specific car listing by ID
Attacks that exploit this kind of access
The rule that runs vehicle.carmarket.listing safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vehicle.carmarket.listing, this is the rule to start with:
vehicle.carmarket.listing is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every vehicle.carmarket.listing call is checked against it from then on.
Questions about vehicle.carmarket.listing
Get full details for a specific car listing by ID — VIN, price, MSRP, mileage, full build specs (engine, transmission, drivetrain, fuel type), dealer contact, Carfax 1-owner status, days on market, photos. Get listing IDs from carmarket.search (MarketCheck). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
vehicle.carmarket.listing accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for vehicle.carmarket.listing: 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 Apibase. Nothing to install.
vehicle.carmarket.listing 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 vehicle.carmarket.listing 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 vehicle.carmarket.listing. 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.
vehicle.carmarket.listing is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue