unlock_vehicle · Smartcar MCP Server MCP: Risk & Policy

WHAT IT DOES

What unlock_vehicle does on Smartcar MCP Server

AI agents invoke unlock_vehicle to trigger actions in Smartcar MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why unlock_vehicle needs a policy

This tool triggers a physical real-world action — unlocking a vehicle's doors. It is not merely reading data or writing a record; it executes an external command via Smartcar's API that has immediate physical consequences (doors become unlocked). While reversible in principle (doors can be re-locked), unauthorized use could compromise vehicle security and passenger safety, warranting a high severity rating.

From the tool's definition Unlock the doors of a vehicle

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

unlock_vehicle Rate-limited

unlock_vehicle stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "unlock_vehicle": {
      "limits": [
        {
          "counter": "unlock_vehicle_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Smartcar MCP Server, so you can run agents against it safely.

FAQ

Questions about unlock_vehicle

What does the unlock_vehicle tool do? +

Unlock the doors of a vehicle. It is categorised as a Execute tool in the Smartcar MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on unlock_vehicle? +

Register the Smartcar MCP Server MCP server in PolicyLayer and add a rule for unlock_vehicle: 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 Smartcar MCP Server. Nothing to install.

What risk level is unlock_vehicle? +

unlock_vehicle is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit unlock_vehicle? +

Yes. Add a rate_limit block to the unlock_vehicle 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.

How do I block unlock_vehicle completely? +

Set action: deny in the PolicyLayer policy for unlock_vehicle. 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.

What MCP server provides unlock_vehicle? +

unlock_vehicle is provided by the Smartcar MCP Server MCP server (thachdosc/smartcar-mcp-test). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.