update_asset_metadata · AEM Assets MCP Server MCP

WHAT IT DOES

What update_asset_metadata does on AEM Assets MCP Server

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

WHY IT NEEDS A POLICY

Why update_asset_metadata needs a policy

This tool modifies asset metadata in AEM, which is a Write operation (data is created/changed reversibly). It does not delete assets (Destructive), move money (Financial), or execute arbitrary code (Execute). Severity is medium because unintended metadata changes could affect asset discoverability and workflows, but the impact is reversible—metadata can be corrected. Confidence is slightly reduced (0.85 vs.

From the tool's definition Tool name 'update_asset_metadata' indicates metadata modification. Server description states it 'perform[s] bulk metadata updates' and the sibling tool 'bulk_update_metadata' confirms this server's write capabilities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_asset_metadata Rate-limited

update_asset_metadata 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": {
    "update_asset_metadata": {
      "limits": [
        {
          "counter": "update_asset_metadata_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 AEM Assets MCP Server, so you can run agents against it safely.

FAQ

Questions about update_asset_metadata

What does the update_asset_metadata tool do? +

update_asset_metadata. It is categorised as a Write tool in the AEM Assets MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_asset_metadata? +

Register the AEM Assets MCP Server MCP server in PolicyLayer and add a rule for update_asset_metadata: 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 AEM Assets MCP Server. Nothing to install.

What risk level is update_asset_metadata? +

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

Can I rate-limit update_asset_metadata? +

Yes. Add a rate_limit block to the update_asset_metadata 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 update_asset_metadata completely? +

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

update_asset_metadata is provided by the AEM Assets MCP Server MCP server (satoshiinoue/aem-assets-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.