model_clone
AI agents use model_clone to create or update resources in Flex Sensor Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Flex Sensor Agent environment.
Cloning a model creates a new simulation model object (reversible write operation). This is not destructive since the original model persists and the operation can be undone by deleting the clone. It is not Execute since it doesn't run computations or trigger external operations—it merely duplicates an existing model structure.
From the tool's definition Tool named 'model_clone' in a COMSOL simulation server context where sibling tools include 'flex_sensor_build_contact_model' and 'flex_sensor_export_contact_results'. The name 'clone' indicates duplication/copying of a model object, which creates new data.
Attacks that exploit this kind of access
model_clone. It is categorised as a Write tool in the Flex Sensor Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Flex Sensor Agent 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 Flex Sensor Agent. 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 Flex Sensor Agent MCP server (tonghui666/flex-sensor-agent-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 →