site_get_logs

Get site access and error 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/site-get-logs.md

WHAT IT DOES

What site_get_logs does on Aapanel

AI agents call site_get_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.

RISK

Why site_get_logs is rated Low

This tool retrieves and queries log files (access logs and error logs) from a website. It performs a read-only operation that returns information without creating, modifying, deleting, or executing anything. The verb 'Get' is a clear indicator of a Read operation.

From the tool's definition Tool name 'site_get_logs' and description 'Get site access and error logs' indicate retrieval of existing log data with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs site_get_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 site_get_logs, this is the rule to start with:

site_get_logs Allowed

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

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 site_get_logs call is checked against it from then on.

FAQ

Questions about site_get_logs

What does the site_get_logs tool do? +

Get site access and error 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 site_get_logs? +

Register the Aapanel MCP server in PolicyLayer and add a rule for site_get_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.

What risk level is site_get_logs? +

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

Can I rate-limit site_get_logs? +

Yes. Add a rate_limit block to the site_get_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.

How do I block site_get_logs completely? +

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

What MCP server provides site_get_logs? +

site_get_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.

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 →