aem_set_context · Adobe Experience Assets Dev MCP

WHAT IT DOES

What aem_set_context does on Adobe Experience Assets Dev MCP

AI agents use aem_set_context to create or update resources in Adobe Experience Assets Dev MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adobe Experience Assets Dev MCP environment.

WHY IT NEEDS A POLICY

Why aem_set_context needs a policy

This tool creates or modifies session-level configuration state reversibly. While it does not directly manipulate assets or data objects, it writes to session context which could affect how other tools on the server behave. The change is reversible (a new session context can be set). This is Write-class activity.

From the tool's definition Tool name 'aem_set_context' and description indicates it 'Set session-level AEM integration defaults' — this modifies session state and configuration that affects subsequent tool behavior and API request routing.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

aem_set_context Rate-limited

aem_set_context stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "aem_set_context": {
      "limits": [
        {
          "counter": "aem_set_context_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Adobe Experience Assets Dev MCP, so you can run agents against it safely.

FAQ

Questions about aem_set_context

What does the aem_set_context tool do? +

Set session-level AEM integration defaults to improve routing and request blueprint accuracy across tools. It is categorised as a Write tool in the Adobe Experience Assets Dev MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on aem_set_context? +

Register the Adobe Experience Assets Dev MCP server in PolicyLayer and add a rule for aem_set_context: 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.

What risk level is aem_set_context? +

aem_set_context is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit aem_set_context? +

Yes. Add a rate_limit block to the aem_set_context 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.

How do I block aem_set_context completely? +

Set action: deny in the PolicyLayer policy for aem_set_context. 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.

What MCP server provides aem_set_context? +

aem_set_context 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.