AI agents use cja_create_segment to create or update resources in Adobe Cja — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adobe Cja environment.
This tool creates segments in CJA, which modifies the analytics configuration reversibly (segments can typically be edited or deleted). This is a Write operation rather than Execute because it creates a defined analytical construct, not arbitrary code execution.
From the tool's definition Tool name 'cja_create_segment' indicates creation of a segment in Adobe Customer Journey Analytics. The naming pattern aligns with other write operations on this server like 'cja_create_calculated_metric'.
Attacks that exploit this kind of access
cja_create_segment. It is categorised as a Write tool in the Adobe Cja MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Adobe Cja MCP server in PolicyLayer and add a rule for cja_create_segment: 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 Adobe Cja. Nothing to install.
cja_create_segment 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 cja_create_segment 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 cja_create_segment. 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.
cja_create_segment is provided by the Adobe Cja MCP server (markhilton/adobe-cja-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
cja_create_segment is one line of Adobe Cja's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →