List campaigns you
AI agents call listActiveCampaigns to retrieve information from Affilync MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays a list of active campaigns from the Affilync platform. It has no side effects—no data is created, modified, deleted, or financial transactions are initiated. It is purely informational retrieval, fitting the 'Read' category. Severity is low because misuse (e.g., listing campaigns repeatedly) poses minimal risk.
From the tool's definition Tool name 'listActiveCampaigns' and context indicating it lists/retrieves campaign data. Description is incomplete ('List campaigns you') but the sibling tools and server description confirm this is a query operation for viewing affiliate campaigns without…
Attacks that exploit this kind of access
List campaigns you. It is categorised as a Read tool in the Affilync MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Affilync MCP Server MCP server in PolicyLayer and add a rule for listActiveCampaigns: 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.
listActiveCampaigns is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listActiveCampaigns 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 listActiveCampaigns. 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.
listActiveCampaigns 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 →