List all features (boundary conditions, domain settings) in a physics interface.
AI agents call physics_list_features 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 is a read-only operation that queries and retrieves metadata about simulation features. It has no side effects, does not execute simulations, does not modify data, and does not delete or create resources. The action is purely informational, consistent with the 'Read' category (retrieves or queries data; no side effects).
From the tool's definition Tool name 'physics_list_features' with description 'List all features (boundary conditions, domain settings) in a physics interface' indicates a retrieval/query operation that returns information about existing simulation configuration without modifying state.
Attacks that exploit this kind of access
List all features (boundary conditions, domain settings) in a physics interface. 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 physics_list_features: 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.
physics_list_features 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 physics_list_features 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 physics_list_features. 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.
physics_list_features 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 →