Create an affiliate network.
AI agents use keitaro_create_affiliate_network to create or update resources in Keitaro MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Keitaro MCP Server environment.
This tool creates a new affiliate network record, which is a reversible write operation. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), involve financial transactions (would be Financial), or merely read data (would be Read).
From the tool's definition Tool name contains 'create' and description states 'Create an affiliate network,' indicating the tool creates and adds new data to the system.
Attacks that exploit this kind of access
Create an affiliate network. It is categorised as a Write tool in the Keitaro MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Keitaro MCP Server MCP server in PolicyLayer and add a rule for keitaro_create_affiliate_network: 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 Keitaro MCP Server. Nothing to install.
keitaro_create_affiliate_network 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 keitaro_create_affiliate_network 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 keitaro_create_affiliate_network. 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.
keitaro_create_affiliate_network is provided by the Keitaro MCP Server MCP server (keitaromanager/keitaro-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 →