Low Risk

vehicles_lookup

Vehicle lookup by plate / chassis / RENAVAM — make, model, year, color, fuel, FIPE price, ownership history, restrictions. POST /v1/datasets/vehicles.

How to control vehicles_lookup ↓

What vehicles_lookup does on Mcp Afip

AI agents call vehicles_lookup to retrieve information from Mcp Afip without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why vehicles_lookup needs a policy

This tool retrieves vehicle registration and property data based on identifiers. While it accesses potentially sensitive ownership and restriction information, the operation is read-only with no side effects. The use of POST for a lookup is a query operation.

From the tool's definition Tool description states 'Vehicle lookup by plate / chassis / RENAVAM' with retrieval of attributes like 'make, model, year, color, fuel, FIPE price, ownership history, restrictions.' The endpoint POST /v1/datasets/vehicles indicates a read/query operation…

Documented attack patterns abuse exactly the kind of access vehicles_lookup gives an agent:

How to control vehicles_lookup

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Afip, and nothing reaches the server without passing your rules. This is the rule we recommend for vehicles_lookup:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "vehicles_lookup": {}
  }
}

vehicles_lookup is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Afip — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about vehicles_lookup

What does the vehicles_lookup tool do? +

Vehicle lookup by plate / chassis / RENAVAM — make, model, year, color, fuel, FIPE price, ownership history, restrictions. POST /v1/datasets/vehicles. It is categorised as a Read tool in the Mcp Afip MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vehicles_lookup? +

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

What risk level is vehicles_lookup? +

vehicles_lookup is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit vehicles_lookup? +

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

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

vehicles_lookup is provided by the Mcp Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Afip tool call.

Start from Mcp Afip, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

1300 Mcp Afip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.