Preflight validator for AEM integration plans. Checks required steps, safeguards, policy controls, unknown steps, and coverage against strict presets.
AI agents call aem_validate_integration_plan to retrieve information from Adobe Experience Assets Dev MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a validation/preflight tool that analyzes and reports on integration plan configurations. It retrieves and examines data (the integration plan) to provide feedback, but does not create, modify, delete, or execute any actual operations. It functions as a Read operation - querying and assessing existing data without side effects.
From the tool's definition Tool description states it 'Checks required steps, safeguards, policy controls, unknown steps, and coverage against strict presets.' The verb 'checks' and 'validate' indicate inspection and analysis of existing integration plans without modification,…
Attacks that exploit this kind of access
Preflight validator for AEM integration plans. Checks required steps, safeguards, policy controls, unknown steps, and coverage against strict presets. It is categorised as a Read tool in the Adobe Experience Assets Dev MCP MCP Server, which means it retrieves data without modifying state.
Register the Adobe Experience Assets Dev MCP server in PolicyLayer and add a rule for aem_validate_integration_plan: 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 Experience Assets Dev MCP. Nothing to install.
aem_validate_integration_plan 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 aem_validate_integration_plan 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 aem_validate_integration_plan. 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.
aem_validate_integration_plan is provided by the Adobe Experience Assets Dev MCP server (stubbedev/adobe-experience-dev-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 →