get_admin_user_login_history

Lấy lịch sử đăng nhập của user

Server ServiceDesk Plus MCP Server thichcode/servicedeskplus_mcp
Category Read
Risk class Low
Parameters 00 required

What get_admin_user_login_history does on ServiceDesk Plus MCP Server

AI agents call get_admin_user_login_history to retrieve information from ServiceDesk Plus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_admin_user_login_history needs a policy

The tool queries and returns historical login data for admin users. While this is fundamentally a Read operation (no data is modified), the sensitivity is elevated to medium severity because login history can reveal security-relevant information such as access patterns, potential unauthorized access, account takeover indicators, and timing of administrative activities.

From the tool's definition Tool name is 'get_admin_user_login_history' and description indicates it retrieves login history of a user ('Lấy lịch sử đăng nhập của user' translates to 'Get login history of user'). This is a data retrieval operation with no modification or side effects.

Questions about get_admin_user_login_history

What does the get_admin_user_login_history tool do? +

Lấy lịch sử đăng nhập của user. It is categorised as a Read tool in the ServiceDesk Plus MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_admin_user_login_history? +

Register the ServiceDesk Plus MCP Server MCP server in PolicyLayer and add a rule for get_admin_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 ServiceDesk Plus MCP Server. Nothing to install.

What risk level is get_admin_user_login_history? +

get_admin_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_admin_user_login_history? +

Yes. Add a rate_limit block to the get_admin_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_admin_user_login_history completely? +

Set action: deny in the PolicyLayer policy for get_admin_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_admin_user_login_history? +

get_admin_user_login_history is provided by the ServiceDesk Plus MCP Server MCP server (thichcode/servicedeskplus_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.