Low Risk

list_customers

List customers with optional filters. Returns paginated results via since_id cursor. If has_more=true, call again with next_since_id.

How to control list_customers ↓

What list_customers does on Sapo

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

Low Risk

Why list_customers needs a policy

This tool queries and retrieves customer data without modifying, deleting, or executing operations. It is a read-only operation with pagination support, typical of data listing endpoints. The blast radius of misuse is minimal (exposure of customer data is a concern, but the operation itself is non-destructive and non-executable). Confidence is high due to clear language indicating a retrieval operation.

From the tool's definition 'List customers with optional filters. Returns paginated results' indicates data retrieval with no side effects.

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

How to control list_customers

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

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

list_customers 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 Sapo — 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_customers

What does the list_customers tool do? +

List customers with optional filters. Returns paginated results via since_id cursor. If has_more=true, call again with next_since_id. It is categorised as a Read tool in the Sapo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_customers? +

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

What risk level is list_customers? +

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

Can I rate-limit list_customers? +

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

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

list_customers is provided by the Sapo MCP server (nguyennguyenit/sapo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sapo tool call.

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

93 Sapo 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.