name_selection · ChimeraX MCP Server MCP: Risk & Policy

WHAT IT DOES

What name_selection does on ChimeraX MCP Server

AI agents use name_selection 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.

WHY IT NEEDS A POLICY

Why name_selection needs a policy

This tool creates or modifies stored selection metadata (a named selection), which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or trigger external operations with unpredictable side effects.

From the tool's definition The tool 'name_selection' performs a 'Save current selection under a reusable name' operation, which creates and stores a named reference to a selection state. This is a reversible data creation action with no destructive or external effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

name_selection Rate-limited

name_selection 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": {
    "name_selection": {
      "limits": [
        {
          "counter": "name_selection_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 ChimeraX MCP Server, so you can run agents against it safely.

FAQ

Questions about name_selection

What does the name_selection tool do? +

Save current selection under a reusable name. 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.

How do I enforce a policy on name_selection? +

Register the ChimeraX MCP Server MCP server in PolicyLayer and add a rule for name_selection: 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.

What risk level is name_selection? +

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

Can I rate-limit name_selection? +

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

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

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