results_export_image
AI agents use results_export_image 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.
The tool exports simulation results as image files, which creates new files on disk (Write category). This is reversible—exported files can be deleted. Severity is medium because exporting data could expose sensitive simulation details, but the operation itself is non-destructive and doesn't execute arbitrary code or affect financial systems.
From the tool's definition Tool name 'results_export_image' and server context indicate image file export functionality. Description is empty, limiting certainty.
Attacks that exploit this kind of access
results_export_image. 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 results_export_image: 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.
results_export_image 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 results_export_image 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 results_export_image. 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.
results_export_image 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 →