Get the progress of the current solving operation.
AI agents call study_get_progress to retrieve information from Flex Sensor Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves progress information from an ongoing simulation in COMSOL Multiphysics. It is purely observational—it reads state without side effects, side-effects, or modifications. No data is created, modified, deleted, or financial operations are performed. This is a straightforward Read category tool.
From the tool's definition Tool name 'study_get_progress' and description 'Get the progress of the current solving operation' indicate a query operation that retrieves status information without modifying or executing any operations.
Attacks that exploit this kind of access
Get the progress of the current solving operation. It is categorised as a Read tool in the Flex Sensor Agent MCP Server, which means it retrieves data without modifying state.
Register the Flex Sensor Agent MCP server in PolicyLayer and add a rule for study_get_progress: 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.
study_get_progress is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the study_get_progress 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 study_get_progress. 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.
study_get_progress 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 →