delete_user_referrer
AI agents call delete_user_referrer to permanently remove resources in Fuul MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the description is uninformative, the explicit 'delete' action combined with the server's financial/affiliate context (managing payouts, incentives) and consistent destructive operations among siblings makes this clearly a Destructive operation. Deleting referrer relationships could break affiliate chains and payout chains irreversibly.
From the tool's definition Tool name 'delete_user_referrer' contains the verb 'delete', which indicates irreversible removal of data.
Attacks that exploit this kind of access
delete_user_referrer. It is categorised as a Destructive tool in the Fuul MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fuul MCP Server MCP server in PolicyLayer and add a rule for delete_user_referrer: 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 Fuul MCP Server. Nothing to install.
delete_user_referrer 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 delete_user_referrer 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 delete_user_referrer. 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.
delete_user_referrer is provided by the Fuul MCP Server MCP server (kuyen-labs/mcp_server). 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 →