Root cause analysis from failure history (LLM-enhanced when OPENAI_API_KEY set, rule-based otherwise).
AI agents call suggest_root_cause 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.
The tool reads failure history and generates a root cause suggestion, either via LLM inference or rule-based logic. It does not create, modify, delete, or trigger any external operation. It is purely analytical/read-only. Severity is low because misuse would at worst surface an incorrect diagnosis, not cause system changes.
From the tool's definition 'Root cause analysis from failure history' — retrieves and analyzes historical data, producing a suggestion/recommendation with no stated side effects
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Root cause analysis from failure history (LLM-enhanced when OPENAI_API_KEY set, rule-based otherwise). 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 suggest_root_cause: 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.
suggest_root_cause 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 suggest_root_cause 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 suggest_root_cause. 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.
suggest_root_cause 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 →