get_user_login_history

Track user login activities and history

SERVERCloudStack MCP Server SOURCEmozg31337/cloudstack-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mozg31337-cloudstack-mcp-server/get-user-login-history.md

WHAT IT DOES

What get_user_login_history does on CloudStack MCP Server

AI agents call get_user_login_history to retrieve information from CloudStack MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_user_login_history is rated Low

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

RECOMMENDED RULE

The rule that runs get_user_login_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CloudStack MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_user_login_history, this is the rule to start with:

get_user_login_history Allowed

get_user_login_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_user_login_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CloudStack MCP Server, apply this rule, and every get_user_login_history call is checked against it from then on.

FAQ

Questions about get_user_login_history

What does the get_user_login_history tool do? +

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.

How do I enforce a policy on get_user_login_history? +

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.

What risk level is get_user_login_history? +

get_user_login_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_user_login_history? +

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.

How do I block get_user_login_history completely? +

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.

What MCP server provides get_user_login_history? +

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.

KEEP EXPLORING

More on CloudStack MCP Server, and thousands of servers like it.

This server

All 442 CloudStack MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →