results_export_data · Flex Sensor Agent MCP: Risk & Policy

WHAT IT DOES

What results_export_data does on Flex Sensor Agent

AI agents use results_export_data 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.

WHY IT NEEDS A POLICY

Why results_export_data needs a policy

Data export typically writes/outputs simulation results to files or external formats. This is reversible (files can be deleted, workflows re-run), making it Write rather than Destructive. The medium severity reflects that exported data could be used downstream by an agent without proper validation, but the operation itself is not immediately destructive.

From the tool's definition Tool name 'results_export_data' indicates data export operation. Server context shows this is part of a COMSOL simulation workflow where 'result export' is explicitly mentioned in the server description. Empty description limits precision.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

results_export_data Rate-limited

results_export_data 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": {
    "results_export_data": {
      "limits": [
        {
          "counter": "results_export_data_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 Flex Sensor Agent, so you can run agents against it safely.

FAQ

Questions about results_export_data

What does the results_export_data tool do? +

results_export_data. 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.

How do I enforce a policy on results_export_data? +

Register the Flex Sensor Agent MCP server in PolicyLayer and add a rule for results_export_data: 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.

What risk level is results_export_data? +

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

Can I rate-limit results_export_data? +

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

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

results_export_data 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.