Retrieve work order and failure history for an asset.
AI agents call get_asset_history to retrieve information from Maximo Enterprise MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing data (work order and failure history) with no side effects. It matches the 'Read' category definition of fetching information. Severity is low because accessing historical data poses minimal risk even if misused by an AI agent—it does not delete, modify, execute code, or create financial obligations.
From the tool's definition Tool name 'get_asset_history' and description 'Retrieve work order and failure history for an asset' indicate a query operation that returns historical data without modifying or executing anything.
Attacks that exploit this kind of access
Retrieve work order and failure history for an asset. It is categorised as a Read tool in the Maximo Enterprise MCP MCP Server, which means it retrieves data without modifying state.
Register the Maximo Enterprise MCP server in PolicyLayer and add a rule for get_asset_history: 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 Maximo Enterprise MCP. Nothing to install.
get_asset_history 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_history 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_history. 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_history is provided by the Maximo Enterprise MCP server (maximo-enterprise-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 →