Get information about an asset's rules engine status and configuration.
AI agents call get_asset_engine_info to retrieve information from OpenRemote MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about an asset's rules engine status and configuration. The verb 'Get' and the absence of any language suggesting modification, deletion, or execution of operations clearly indicate a read-only operation. No data is created, modified, deleted, or irreversibly changed.
From the tool's definition Tool name 'get_asset_engine_info' and description 'Get information about an asset's rules engine status and configuration' indicate retrieval of existing data without modification or side effects.
Attacks that exploit this kind of access
Get information about an asset's rules engine status and configuration. It is categorised as a Read tool in the OpenRemote MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenRemote MCP Server MCP server in PolicyLayer and add a rule for get_asset_engine_info: 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 OpenRemote MCP Server. Nothing to install.
get_asset_engine_info 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 get_asset_engine_info 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 get_asset_engine_info. 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.
get_asset_engine_info is provided by the OpenRemote MCP Server MCP server (openremote/service-mcp-server). 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 →