This record as markdown: /tools/aapanel-mcp/database-get-info.md
What database_get_info does on Aapanel
AI agents call database_get_info 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 database_get_info is rated Low
This tool queries and retrieves database information without creating, modifying, deleting, or executing operations. It is a pure read operation with minimal risk—the only concern would be exposure of sensitive database metadata, but this is a standard informational query. Severity is low because read-only access to database details does not enable data theft or system compromise on its own.
From the tool's definition Tool name 'database_get_info' and description 'Get database details' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs database_get_info 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 database_get_info, this is the rule to start with:
database_get_info 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 database_get_info call is checked against it from then on.
Questions about database_get_info
Get database details. 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 database_get_info: 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.
database_get_info 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 database_get_info 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 database_get_info. 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.
database_get_info 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