Create a traffic source.
AI agents use keitaro_create_traffic_source 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 traffic source configuration, which modifies the system state by adding a new record. This is a Write category action—it creates data but does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool name is 'keitaro_create_traffic_source' and description states 'Create a traffic source.' The verb 'Create' indicates data creation, a reversible write operation.
Attacks that exploit this kind of access
Create a traffic source. 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_traffic_source: 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_traffic_source 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_traffic_source 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_traffic_source. 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_traffic_source 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 →