flex_sensor_export_contact_results · Flex Sensor Agent MCP

WHAT IT DOES

What flex_sensor_export_contact_results does on Flex Sensor Agent

AI agents use flex_sensor_export_contact_results 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 flex_sensor_export_contact_results needs a policy

The tool appears to export simulation data, which is a Write operation (creates or modifies data reversibly). Without an explicit description, confidence is reduced. The severity is medium because exporting results could overwrite existing files or expose sensitive simulation data, but the operation is reversible (files can be deleted or re-exported).

From the tool's definition Tool name 'flex_sensor_export_contact_results' indicates it exports or saves simulation results. The server description mentions 'result export' as a core capability. This tool likely writes results to a file or external format.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

flex_sensor_export_contact_results Rate-limited

flex_sensor_export_contact_results 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": {
    "flex_sensor_export_contact_results": {
      "limits": [
        {
          "counter": "flex_sensor_export_contact_results_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 flex_sensor_export_contact_results

What does the flex_sensor_export_contact_results tool do? +

flex_sensor_export_contact_results. 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 flex_sensor_export_contact_results? +

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

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

Can I rate-limit flex_sensor_export_contact_results? +

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

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

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