record_spin · ChimeraX MCP Server MCP: Risk & Policy

WHAT IT DOES

What record_spin does on ChimeraX MCP Server

AI agents use record_spin 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 record_spin needs a policy

This tool creates and writes video output to disk. It is not destructive because the video file can be removed; it is not read-only because it produces persistent artifacts. The severity is medium because misuse could fill disk space or create unwanted files, but the impact is localized to the ChimeraX session and file system, not a widespread or irreversible damage vector.

From the tool's definition The tool 'record_spin' performs a 'save as video' operation, creating a new file artifact that persists after execution. This is a reversible write operation—the video file can be deleted or overwritten.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_spin Rate-limited

record_spin 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": {
    "record_spin": {
      "limits": [
        {
          "counter": "record_spin_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 record_spin

What does the record_spin tool do? +

Record a full turntable spin and save as video in one step. 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 record_spin? +

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

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

Can I rate-limit record_spin? +

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

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

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