Track user login activities and history
AI agents call get_user_login_history to retrieve information from CloudStack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical login data for auditing purposes. It performs a non-destructive query operation with no side effects on infrastructure or data state. While login history could be sensitive information, the risk category is determined by the operation type (read), not data sensitivity.
From the tool's definition Tool name 'get_user_login_history' and description 'Track user login activities and history' indicate data retrieval without modification. The verb 'get' and action 'track/history' are read-only operations that query existing audit logs.
Attacks that exploit this kind of access
Track user login activities and history. It is categorised as a Read tool in the CloudStack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for get_user_login_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 CloudStack MCP Server. Nothing to install.
get_user_login_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 get_user_login_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 get_user_login_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.
get_user_login_history is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-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 →