security_get_operation_logs
Get panel operation logs (all actions performed through the panel).
This record as markdown: /tools/aapanel-mcp/security-get-operation-logs.md
What security_get_operation_logs does on Aapanel
AI agents call security_get_operation_logs 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.
Why security_get_operation_logs is rated Low
This tool retrieves and queries operation logs, which is a read-only operation with no side effects. However, the severity is medium rather than low because operation logs may contain sensitive information about administrative actions, credentials in URLs, or other confidential data that could be exploited if an agent misuses access to these logs.
From the tool's definition Tool name contains 'get' and description states 'Get panel operation logs'; retrieves historical data of actions without modifying or executing operations.
Attacks that exploit this kind of access
The rule that runs security_get_operation_logs 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 security_get_operation_logs, this is the rule to start with:
security_get_operation_logs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aapanel, apply this rule, and every security_get_operation_logs call is checked against it from then on.
Questions about security_get_operation_logs
Get panel operation logs (all actions performed through the panel). It is categorised as a Read tool in the Aapanel MCP Server, which means it retrieves data without modifying state.
Register the Aapanel MCP server in PolicyLayer and add a rule for security_get_operation_logs: 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.
security_get_operation_logs 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 security_get_operation_logs 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 security_get_operation_logs. 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.
security_get_operation_logs 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.
More on Aapanel, and thousands of servers like it.
This server
Across the catalogue