Generate ready-to-use Maximo API code in Python, JavaScript, curl, or SQL.
AI agents invoke generate_api_code to trigger actions in Maximo Enterprise MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool generates executable code (Python, JavaScript, curl, SQL) intended to be run against a Maximo system. While code generation itself is a write/read operation, the primary purpose is to produce executable artifacts that, when run, could perform any operation including destructive ones (especially SQL).
From the tool's definition 'Generate ready-to-use Maximo API code in Python, JavaScript, curl, or SQL'
Attacks that exploit this kind of access
Generate ready-to-use Maximo API code in Python, JavaScript, curl, or SQL. It is categorised as a Execute tool in the Maximo Enterprise MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Maximo Enterprise MCP server in PolicyLayer and add a rule for generate_api_code: 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_api_code is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the generate_api_code 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_api_code. 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_api_code 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 →