Check if OpenEMS is installed and available for running simulations.
AI agents call openems_check_installation to retrieve information from Mcp Openems without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves system state information (whether OpenEMS is installed) without modifying, executing, or deleting anything. It is purely informational/diagnostic in nature, making it a Read operation with minimal risk.
From the tool's definition Tool name 'openems_check_installation' and description 'Check if OpenEMS is installed and available' indicate a status query with no side effects.
Attacks that exploit this kind of access
Check if OpenEMS is installed and available for running simulations. It is categorised as a Read tool in the Mcp Openems MCP Server, which means it retrieves data without modifying state.
Register the Mcp Openems MCP server in PolicyLayer and add a rule for openems_check_installation: 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 Mcp Openems. Nothing to install.
openems_check_installation 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 openems_check_installation 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 openems_check_installation. 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.
openems_check_installation is provided by the Mcp Openems MCP server (rfingadam/mcp-openems). 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 →