Set an attribute on an element
AI agents use dom_set_attr to create or update resources in Claude Imagine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Imagine environment.
This tool creates or modifies element attributes in the DOM, which is a write operation with potential side effects depending on which attributes are modified (e.g., setting onclick handlers, href, form actions, or data attributes). However, it is reversible—attributes can be changed back or removed. It does not execute code directly, delete data, or move money.
From the tool's definition Tool name 'dom_set_attr' and description 'Set an attribute on an element' indicate modification of DOM elements. This is a write operation that changes element properties (class, id, data attributes, ARIA attributes, etc.) in a reversible manner.
Attacks that exploit this kind of access
Set an attribute on an element. It is categorised as a Write tool in the Claude Imagine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Imagine MCP server in PolicyLayer and add a rule for dom_set_attr: 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 Claude Imagine. Nothing to install.
dom_set_attr 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 dom_set_attr 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 dom_set_attr. 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.
dom_set_attr is provided by the Claude Imagine MCP server (t3rm1nu55/claudeimagine). 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 →