get_postgresql_instance

What get_postgresql_instance does on Linode MCP Server

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

Why get_postgresql_instance is rated Low

This tool retrieves information about an existing PostgreSQL database instance. It performs a query operation to fetch metadata or configuration details, which is a read-only action. There is no capability to modify, delete, execute code, or trigger financial actions. The blast radius of misuse is minimal - an attacker could learn about database configurations but cannot alter or damage resources.

From the tool's definition Tool name is 'get_postgresql_instance' and description states 'Get details for a specific PostgreSQL database instance' - the verb 'Get' and action 'details' indicate data retrieval with no modification or side effects.

The rule that runs get_postgresql_instance safely

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_postgresql_instance": {}
  }
}

Questions about get_postgresql_instance