remove_user_from_referral_code
AI agents call remove_user_from_referral_code 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.
The name suggests removing a user from a referral code, which is likely a destructive/irreversible operation affecting affiliate tracking and potentially payouts. Given the server context (affiliate programs, payouts), misuse could break referral chains and financial attribution.
From the tool's definition Tool name 'remove_user_from_referral_code' implies irreversible removal of a user association; description is empty and uninformative, lowering confidence.
Attacks that exploit this kind of access
remove_user_from_referral_code. 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 remove_user_from_referral_code: 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.
remove_user_from_referral_code 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 remove_user_from_referral_code 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 remove_user_from_referral_code. 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.
remove_user_from_referral_code 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 →