model_clone
AI agents use model_clone 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.
Cloning a model in COMSOL likely creates a new copy of an existing simulation model, which constitutes a Write operation (reversible data creation). The severity is medium because creating duplicate models could consume resources or lead to confusion in model management, but the action is reversible and doesn't destroy data or execute arbitrary code. Confidence is moderate due to the absent description.
From the tool's definition Tool name 'model_clone' and the context of COMSOL Multiphysics simulation automation suggest creation/duplication of model data. No description provided, so assessment is limited.
Attacks that exploit this kind of access
model_clone. 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.
Register the COMSOL MCP Server MCP server in PolicyLayer and add a rule for model_clone: 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.
model_clone 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 model_clone 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 model_clone. 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.
model_clone 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.
model_clone is one line of COMSOL MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →