Synthesize a step-by-step runbook from past WO resolutions on this and similar-type assets.
AI agents call generate_runbook_from_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.
The tool reads historical work order resolution data and synthesizes it into a runbook document. It retrieves and aggregates existing data without modifying any records or triggering external operations. The output is a generated document based on past data, making it a read/query operation.
From the tool's definition Synthesize a step-by-step runbook from past WO resolutions on this and similar-type assets
Attacks that exploit this kind of access
Synthesize a step-by-step runbook from past WO resolutions on this and similar-type assets. 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 generate_runbook_from_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.
generate_runbook_from_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 generate_runbook_from_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 generate_runbook_from_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.
generate_runbook_from_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 →