AI agents call list_object_structures to retrieve information from Maximo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates available API object structures from Maximo's schema. It performs a read-only query operation with no side effects—no data is created, modified, deleted, or executed. The optional filtering is applied to the retrieval results, not to Maximo's state. This is a classic Read category operation with low blast radius if misused by an AI agent.
From the tool's definition Tool name is 'list_object_structures' and description states 'List available Maximo Object Structures (APIs) from the schema, with optional filtering.' The verb 'list' indicates retrieval/enumeration of existing schema metadata without modification.
Attacks that exploit this kind of access
List available Maximo Object Structures (APIs) from the schema, with optional filtering. It is categorised as a Read tool in the Maximo MCP Server, which means it retrieves data without modifying state.
Register the Maximo MCP server in PolicyLayer and add a rule for list_object_structures: 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. Nothing to install.
list_object_structures 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_object_structures 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_object_structures. 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_object_structures is provided by the Maximo MCP server (maximo-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 →