List all affiliates working with your brand
AI agents call listBrandAffiliates 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 affiliate information for display/query purposes. There is no creation, modification, deletion, or execution of external operations. The data returned is metadata about existing affiliate relationships. While this could reveal business information, the impact is limited to information disclosure without ability to modify or take action on the platform.
From the tool's definition Tool name 'listBrandAffiliates' and description 'List all affiliates working with your brand' indicate a retrieval operation with no side effects. The verb 'list' is a classic Read operation.
Attacks that exploit this kind of access
List all affiliates working with your brand. 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 listBrandAffiliates: 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.
listBrandAffiliates 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 listBrandAffiliates 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 listBrandAffiliates. 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.
listBrandAffiliates 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 →