Delete a payee
AI agents call payee_delete to permanently remove resources in Starling Bank — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a payee is an irreversible action that removes stored payment recipient information. While not directly moving money, it destructively modifies account configuration in a way that cannot be easily undone. This is more severe than Write (reversible modifications) and constitutes Destructive category per the rules.
From the tool's definition Tool name 'payee_delete' explicitly performs deletion. Description states 'Delete a payee', confirming irreversible removal of data from the banking system.
Attacks that exploit this kind of access
Delete a payee. It is categorised as a Destructive tool in the Starling Bank MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Starling Bank MCP server in PolicyLayer and add a rule for payee_delete: 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 Starling Bank. Nothing to install.
payee_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the payee_delete 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 payee_delete. 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.
payee_delete is provided by the Starling Bank MCP server (starling-bank-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →