Apply to join an affiliate campaign. Some campaigns auto-approve.
AI agents use joinCampaign to create or update resources in Affilync MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Affilync MCP Server environment.
This tool creates an application/membership record in a campaign, which is a reversible write action. While some campaigns auto-approve (which could trigger downstream effects like affiliate link generation), the core action is submitting an application or joining a campaign — a data creation operation. It's not financially transactional itself, though it enables future earnings.
From the tool's definition Apply to join an affiliate campaign. Some campaigns auto-approve.
Attacks that exploit this kind of access
Apply to join an affiliate campaign. Some campaigns auto-approve. It is categorised as a Write tool in the Affilync MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Affilync MCP Server MCP server in PolicyLayer and add a rule for joinCampaign: 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 Affilync MCP Server. Nothing to install.
joinCampaign 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 joinCampaign 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 joinCampaign. 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.
joinCampaign is provided by the Affilync MCP Server MCP server (moneyflowz367/affilync-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 →