Add a new address to a customer. Required: address1, city, country.
AI agents use add_customer_address to create or update resources in Sapo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sapo environment.
This tool creates or adds a new address record for a customer, which is a reversible modification of customer data. It does not delete, execute code, transfer funds, or read data without side effects. The severity is low because adding an address has minimal blast radius—it's customer metadata that can be easily modified or removed, and does not affect financial transactions, inventory, or system operations.
From the tool's definition Tool name 'add_customer_address' and description 'Add a new address to a customer' indicate creation of new customer data (address record).
Documented attack patterns abuse exactly the kind of access add_customer_address 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 add_customer_address:
{
"version": "1",
"default": "deny",
"tools": {
"add_customer_address": {
"limits": [
{
"counter": "add_customer_address_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} add_customer_address stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a new address to a customer. Required: address1, city, country. It is categorised as a Write tool in the Sapo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sapo MCP server in PolicyLayer and add a rule for add_customer_address: 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.
add_customer_address is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_customer_address 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 add_customer_address. 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.
add_customer_address 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.