Low Risk

list_sales

List sales in Conta Azul

How to control list_sales ↓

What list_sales does on Mcp Ap2

AI agents call list_sales 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 list_sales needs a policy

The verb 'list' is a read-only operation that retrieves and displays sales records. There is no indication of data creation, modification, deletion, or execution of external operations. This falls squarely into the Read category with low severity, as querying sales data poses minimal risk even if an AI agent accesses it unexpectedly.

From the tool's definition Tool name 'list_sales' and description 'List sales in Conta Azul' indicate a retrieval operation that queries existing sales data without modification.

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

How to control list_sales

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 list_sales:

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

list_sales 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 list_sales

What does the list_sales tool do? +

List sales in Conta Azul. 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 list_sales? +

Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for list_sales: 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 list_sales? +

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

Can I rate-limit list_sales? +

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

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

list_sales 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.