AI agents call cja_get_dataview_info to retrieve information from Adobe Cja without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and context within an analytics query server strongly suggests this retrieves dataview metadata or configuration without modification. The lack of a description lowers confidence slightly, but the operational pattern across sibling tools (cja_get_calculated_metric_details, cja_get_segment_details, cja_get_top_items) indicates consistent read-only retrieval behavior.
From the tool's definition Tool name 'cja_get_dataview_info' indicates a retrieval operation (get) for dataview information. No description provided, but naming convention and sibling tools (list_*, get_*) suggest read-only analytics queries.
Attacks that exploit this kind of access
cja_get_dataview_info. It is categorised as a Read tool in the Adobe Cja MCP Server, which means it retrieves data without modifying state.
Register the Adobe Cja MCP server in PolicyLayer and add a rule for cja_get_dataview_info: 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_get_dataview_info 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 cja_get_dataview_info 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_get_dataview_info. 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_get_dataview_info 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.
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 →