add_vehicle · StockSpark MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_vehicle does on StockSpark MCP Server

AI agents use add_vehicle to create or update resources in StockSpark MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your StockSpark MCP Server environment.

WHY IT NEEDS A POLICY

Why add_vehicle needs a policy

The add_vehicle tool creates new vehicle records in a dealership inventory system. This is a reversible Write operation—data can be created and subsequently modified or deleted. It does not execute code, trigger external operations, or permanently destroy data.

From the tool's definition Tool description states "Create vehicle" which is a data creation operation. The description explicitly mentions "Manual entry" of vehicle data, confirming it modifies the inventory system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_vehicle Rate-limited

add_vehicle stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_vehicle": {
      "limits": [
        {
          "counter": "add_vehicle_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about add_vehicle

What does the add_vehicle tool do? +

Create vehicle with template or basic data. PREFERRED: Use with template from get_vehicle_template for complete specifications FALLBACK: Use with basic data when no template available Template mode includes: Complete technical specs, emissions, equipment Basic mode: Manual entry when no reference data exists. It is categorised as a Write tool in the StockSpark MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_vehicle? +

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

What risk level is add_vehicle? +

add_vehicle is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_vehicle? +

Yes. Add a rate_limit block to the add_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 add_vehicle completely? +

Set action: deny in the PolicyLayer policy for add_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 add_vehicle? +

add_vehicle is provided by the StockSpark MCP Server MCP server (loukach/stockspark-mcp-poc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.