Set the background color (white, black, hex).
AI agents use set_background to create or update resources in ChimeraX MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ChimeraX MCP Server environment.
This tool modifies the display properties of the ChimeraX environment by changing the background color. It creates or modifies display settings reversibly—the user can change the background color back to a previous state at any time. This is a non-destructive modification of the visualization state, not data deletion, code execution, or financial action.
From the tool's definition Tool name 'set_background' and description 'Set the background color (white, black, hex)' indicate modification of visualization state (background color) within ChimeraX.
Attacks that exploit this kind of access
Set the background color (white, black, hex). It is categorised as a Write tool in the ChimeraX MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ChimeraX MCP Server MCP server in PolicyLayer and add a rule for set_background: 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 ChimeraX MCP Server. Nothing to install.
set_background 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 set_background 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 set_background. 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.
set_background is provided by the ChimeraX MCP Server MCP server (mahynotch/chimerax-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 →