swap_user_referral_code
AI agents use swap_user_referral_code to create or update resources in Fuul MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fuul MCP Server environment.
The name 'swap_user_referral_code' suggests modifying or replacing a user's referral code, which is a write operation that could affect affiliate tracking and payouts. Given the server manages affiliate programs and payouts, changing a referral code could have significant downstream financial implications (e.g., mis-attributing commissions). However, since the description is empty, confidence is lowered.
From the tool's definition Tool name: swap_user_referral_code; description is empty
Attacks that exploit this kind of access
swap_user_referral_code. It is categorised as a Write tool in the Fuul MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fuul MCP Server MCP server in PolicyLayer and add a rule for swap_user_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.
swap_user_referral_code 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 swap_user_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 swap_user_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.
swap_user_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 →