Unlock a user account in Maximo by resetting lock status and failed login count
AI agents use unlock_user_account to create or update resources in MCP Maximo Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Maximo Server environment.
This tool modifies user account state by resetting lock status and failed login count — a reversible write operation. However, it carries high severity because unlocking accounts bypasses security controls (account lockout policies exist to prevent brute-force attacks), and an AI agent misusing this tool could enable unauthorized access to enterprise asset management systems.
From the tool's definition Unlock a user account in Maximo by resetting lock status and failed login count
Attacks that exploit this kind of access
Unlock a user account in Maximo by resetting lock status and failed login count. It is categorised as a Write tool in the MCP Maximo Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Maximo Server MCP server in PolicyLayer and add a rule for unlock_user_account: 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 MCP Maximo Server. Nothing to install.
unlock_user_account is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the unlock_user_account 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 unlock_user_account. 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.
unlock_user_account is provided by the MCP Maximo Server MCP server (nick0918964388/mcp-maximo-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 →