Low Risk

get_fipe_brands

List vehicle brands by type from FIPE table

How to control get_fipe_brands ↓

What get_fipe_brands does on Mcp Ap2

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

Low Risk

Why get_fipe_brands needs a policy

This tool retrieves and lists data from a static or reference table. The verb 'List' and the context of querying a FIPE table (a read-only reference database) confirm it performs a query operation with no side effects, data modification, deletion, or financial impact. Despite being on a payment protocol server, this specific tool only reads public reference data about vehicle brands.

From the tool's definition Tool name 'get_fipe_brands' and description 'List vehicle brands by type from FIPE table' indicate a retrieval operation that queries a reference database (FIPE is a Brazilian vehicle pricing table) without modification or side effects.

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

How to control get_fipe_brands

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

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

get_fipe_brands 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 Ap2 — 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 get_fipe_brands

What does the get_fipe_brands tool do? +

List vehicle brands by type from FIPE table. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_fipe_brands? +

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

What risk level is get_fipe_brands? +

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

Can I rate-limit get_fipe_brands? +

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

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

get_fipe_brands is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, 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 Ap2 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.