Lifetime value for a single customer: total revenue, order count, first/last order date.
AI agents call customer_ltv 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.
The tool is purely informational, returning analytical data about a customer's lifetime value and order history. It performs no writes, deletions, executions, or financial transactions. The read-only nature and lack of any state-changing operations place it firmly in the Read category with low severity.
From the tool's definition Tool retrieves customer metrics: 'total revenue, order count, first/last order date' — data querying with no modification or side effects.
Documented attack patterns abuse exactly the kind of access customer_ltv gives an agent:
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 customer_ltv:
{
"version": "1",
"default": "deny",
"tools": {
"customer_ltv": {}
}
}customer_ltv is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lifetime value for a single customer: total revenue, order count, first/last order date. It is categorised as a Read tool in the Sapo MCP Server, which means it retrieves data without modifying state.
Register the Sapo MCP server in PolicyLayer and add a rule for customer_ltv: 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.
customer_ltv is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the customer_ltv 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.
Set action: deny in the PolicyLayer policy for customer_ltv. 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.
customer_ltv 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.
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.