Get the geofences configured for an asset.
AI agents call get_asset_geofences 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 retrieves and queries geofence data associated with an asset without modifying, deleting, or executing any operations. It is a pure Read operation with minimal security impact—exposure of geofence configuration is informational only and does not enable unauthorized modifications, deletions, or external actions.
From the tool's definition Tool name 'get_asset_geofences' and description 'Get the geofences configured for an asset' indicate a retrieval operation with no side effects. Uses 'Get' verb and performs a query of existing geofence configuration data.
Attacks that exploit this kind of access
Get the geofences configured for an asset. 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_geofences: 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_geofences 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_geofences 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_geofences. 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_geofences 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 →