List item-master records — the catalog of stocked and non-stocked items.
AI agents call list_items 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 queries and retrieves inventory catalog data without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval function consistent with Read category tools like 'list' and 'fetch'. The blast radius is minimal—exposure of this tool allows an AI agent to view item inventory metadata but not to alter inventory, execute commands, or commit financial transactions.
From the tool's definition Tool name 'list_items' and description 'List item-master records — the catalog of stocked and non-stocked items' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List item-master records — the catalog of stocked and non-stocked items. 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 list_items: 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.
list_items 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 list_items 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 list_items. 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.
list_items 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 →