config_get_login_log

Get panel login logs.

SERVERAapanel SOURCEnipunanirmal/aapanel-mcp

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/aapanel-mcp/config-get-login-log.md

WHAT IT DOES

What config_get_login_log does on Aapanel

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

RISK

Why config_get_login_log is rated Low

This tool retrieves historical login log data from the aaPanel management interface. It performs a read-only query operation with no side effects, does not execute code or commands, and does not modify any state. The worst-case misuse by an AI agent would be unauthorized information disclosure of login patterns, which has limited blast radius compared to write or destructive operations.

From the tool's definition Tool name 'config_get_login_log' uses 'get' verb and description states 'Get panel login logs', indicating data retrieval with no modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs config_get_login_log safely

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

config_get_login_log Allowed

config_get_login_log 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": {
    "config_get_login_log": {}
  }
}

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

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

FAQ

Questions about config_get_login_log

What does the config_get_login_log tool do? +

Get panel login logs. It is categorised as a Read tool in the Aapanel MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on config_get_login_log? +

Register the Aapanel MCP server in PolicyLayer and add a rule for config_get_login_log: 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 Aapanel. Nothing to install.

What risk level is config_get_login_log? +

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

Can I rate-limit config_get_login_log? +

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

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

config_get_login_log is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aapanel, and thousands of servers like it.

This server

All 282 Aapanel 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 →