# get_vehicle_details

Get full specifications, equipment, all images, and pricing per term for a specific vehicle. Use a vehicle_id from search_vehicles results. IMPORTANT: Always show detail_url as a clickable link — it points to the FINN configurator where the user picks term and km. To produce a direct checkout link for a specific term + km combination (and optionally a one-time Fahrzeugbereitstellung), call get_subscription_pricing and use the checkout_url it returns. Never construct checkout URLs yourself. The vehicle_id field is an internal API identifier — never display it to users.

Agent View of the PolicyLayer registry record for `get_vehicle_details`. HTML page: https://policylayer.com/tools/com-finn-www-auto/get-vehicle-details

## Facts

- Tool: `get_vehicle_details`
- Server: FINN Auto - Car Subscription (`https://www.finn.com/api/mcp`) — https://policylayer.com/tools/com-finn-www-auto.md
- Homepage: https://github.com/finn-auto/finn-auto-ui-frontend
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `vehicle_id` | string | yes | The vehicle product ID (e.g. "bmw-ix1-12345-alpinweissuni") |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_vehicle_details",
    "arguments": {
      "vehicle_id": "<vehicle_id>"
    }
  }
}
```

## Why get_vehicle_details is rated Low

This tool performs data retrieval operations only. It returns vehicle details and generates URLs for user navigation but does not execute transactions, modify data, or trigger external operations. The actual checkout and pricing commitment happen via separate tools (get_subscription_pricing, checkout_url).

From the tool's own definition: "Tool retrieves vehicle specifications, equipment, images, and pricing data. Verbs used: 'Get full specifications', 'points to', 'returns'."

## Use case

AI agents call get_vehicle_details to retrieve information from FINN Auto - Car Subscription without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches FINN Auto - Car Subscription:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_vehicle_details": {}
  }
}
```

## Other tools on FINN Auto - Car Subscription (4)

- `get_available_filters` — Read — https://policylayer.com/tools/com-finn-www-auto/get-available-filters.md
- `get_internal_link_url` — Read — https://policylayer.com/tools/com-finn-www-auto/get-internal-link-url.md
- `get_subscription_pricing` — Read — https://policylayer.com/tools/com-finn-www-auto/get-subscription-pricing.md
- `search_vehicles` — Read — https://policylayer.com/tools/com-finn-www-auto/search-vehicles.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-finn-www-auto · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-finn-www-auto