delete_customer_address

Delete an address book entry. DELETE /customers/{customerId}/addressbooks/{addressId}.

Server Rebillia MCP Server rhinosaas/rebillia-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_customer_address does on Rebillia MCP Server

AI agents call delete_customer_address to permanently remove resources in Rebillia MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_customer_address needs a policy

This tool permanently removes customer address data without possibility of reversal. While destructive, the impact is limited to a single customer address record rather than bulk data or critical infrastructure, warranting medium severity rather than high. The action cannot be undone, placing it firmly in the Destructive category rather than Write (which is reversible).

From the tool's definition Tool name is 'delete_customer_address' and description states 'Delete an address book entry' with DELETE HTTP method, indicating irreversible removal of data.

Questions about delete_customer_address

What does the delete_customer_address tool do? +

Delete an address book entry. DELETE /customers/{customerId}/addressbooks/{addressId}. It is categorised as a Destructive tool in the Rebillia MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_customer_address? +

Register the Rebillia MCP Server MCP server in PolicyLayer and add a rule for delete_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 Rebillia MCP Server. Nothing to install.

What risk level is delete_customer_address? +

delete_customer_address is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_customer_address? +

Yes. Add a rate_limit block to the delete_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.

How do I block delete_customer_address completely? +

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

What MCP server provides delete_customer_address? +

delete_customer_address is provided by the Rebillia MCP Server MCP server (rhinosaas/rebillia-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.