model_save_version · COMSOL MCP Server MCP: Risk & Policy

WHAT IT DOES

What model_save_version does on COMSOL MCP Server

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

WHY IT NEEDS A POLICY

Why model_save_version needs a policy

The tool saves a version of a model, which is a reversible write operation (new version can be created, prior versions retained). This is not destructive since versioning typically preserves history. Severity is medium because unintended model saves could clutter version history or overwrite intended states in a simulation workflow, but the operation remains reversible.

From the tool's definition Tool name 'model_save_version' indicates creation or modification of a versioned model state. The '_save_' prefix strongly suggests persisting data changes. Description is empty, limiting confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

model_save_version Rate-limited

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

FAQ

Questions about model_save_version

What does the model_save_version tool do? +

model_save_version. It is categorised as a Write tool in the COMSOL 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 model_save_version? +

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

What risk level is model_save_version? +

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

Can I rate-limit model_save_version? +

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

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

model_save_version is provided by the COMSOL MCP Server MCP server (zhangyoupeng1996/codex_mcp_comsol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.