How tools are authorized
Tool discovery changes with the authenticated PostgreSQL account. A tool may be hidden if the user lacks its general operation type; even if visible, every actual database operation is still subject to PostgreSQL roles, table and column grants, row-level security, constraints and triggers.
Tool visibility is not permission to access every record. For example, SELECT access to one table may expose select_records, but the user cannot use it to read another table without the required database privileges.
Tool catalog
There are 23 registered tool definitions in this version across five groups. Optional tools are available only when their corresponding feature is enabled.
| Tool | Group | What it does | Required permissions | Available when |
|---|---|---|---|---|
whoami | Core | Show the current PostgreSQL account and broad available operation categories. | Authenticated PostgreSQL login | Always visible |
list_tables | Core | List accessible tables and their table-level privileges. | Authenticated login; results limited by database permissions | Always visible |
describe_table | Core | Inspect accessible columns, types, descriptions and effective column privileges. | Authenticated login; relevant relation/column access | Always visible |
explain_permissions | Core | Inspect grants, RLS policies, triggers and constraints; optionally probe SELECT visibility. Cannot prove arbitrary writes will succeed. | Authenticated login; any SELECT probe still requires database privileges | Always visible |
app_integration_guide | Core | Explain Data-MCP integration for AI-generated forms, reports and dashboards. | Authenticated PostgreSQL login | Always visible |
select_records | Data | Select filtered rows, with ordering and a result limit up to 100. | Relevant SELECT privileges; RLS applies | When user has SELECT somewhere |
insert_record | Data | Insert one record into an authorized table. | INSERT on relevant columns; database rules apply | When user has INSERT somewhere |
update_records | Data | Update filtered rows; mandatory filters and max_rows 1–100 (default 20). | UPDATE on target columns; relevant filter/SELECT rights; RLS | When user has UPDATE somewhere |
delete_records | Data | Delete filtered rows; mandatory filters and max_rows 1–100. | DELETE on table; relevant filter/SELECT rights; RLS | When user has DELETE somewhere |
inspect_database | Admin | Inspect actual PostgreSQL catalogs, schema objects, policies and functions. | Superuser or mcp_admin; catalog visibility still applies | Admin only |
manage_database | Admin | Generate a proposed SQL migration from a natural-language instruction using the internal LLM. Does not apply SQL. | Superuser or mcp_admin; OpenAI key configured for planning | Admin only |
review_plan | Admin | Return a stored plan summary, warnings and proposed SQL for review. | Same administrator and a valid pending plan ID | Admin only |
implement_plan | Admin | Execute a previously approved migration against PostgreSQL. | Same administrator; valid plan ID; confirm=true; actual PostgreSQL DDL privileges | Admin only |
cancel_plan | Admin | Discard a pending migration without changing the database. | Same administrator and a valid pending plan ID | Admin only |
site_list | Hosting | List the logged-in user’s published projects, subfolders, files and URLs. | Authenticated PostgreSQL login; own files only | Standalone deployment |
site_read_file | Hosting | Read one of the user’s published files and its SHA-256 version hash. | Authenticated login; own files only | Standalone deployment |
site_create_file | Hosting | Publish a new HTML/CSS/JS/static asset and create missing folders. | Authenticated login; own user directory; quotas and allowed file types | Standalone deployment |
site_update_file | Hosting | Replace an existing own file with SHA-256 concurrency protection. | Authenticated login; own file and correct expected_sha256 | Standalone deployment |
site_delete_file | Hosting | Remove an own file; optional expected SHA-256 verification. | Authenticated login; own file | Standalone deployment |
site_delete_project | Hosting | Delete an entire own published project and its files. | Authenticated login; own project; confirm=true | Standalone deployment |
rest_api_guide | Legacy REST | Describe legacy direct PostgREST integration and token flow. Not recommended for new generated apps. | Authenticated PostgreSQL login | REST_MCP_TOOLS=true |
rest_relationships | Legacy REST | Inspect readable table foreign-key relationships for REST queries. | USAGE and appropriate SELECT on related structures | REST_MCP_TOOLS=true |
generate_rest_request | Legacy REST | Generate a REST URL, headers, filters and fetch example; does not execute the query. | Corresponding SELECT/INSERT/UPDATE/DELETE and column rights | REST_MCP_TOOLS=true |
No tools match this filter. Try another term.
Core and data tools
Every authenticated account can discover whoami, list_tables, describe_table, explain_permissions and app_integration_guide. Data operations appear when the account has the corresponding privilege somewhere in the database. Filters are structured, not arbitrary SQL, and updates/deletions require filters and cap affected rows.
For cell-level business logic, PostgreSQL may still reject an operation in a trigger or policy after the tool becomes visible. explain_permissions describes the relevant rules but does not execute risky test writes.
Administrator tools
A user must be a PostgreSQL superuser or a member of the mcp_admin role to see administration tools. Membership in mcp_admin alone does not grant unrestricted DDL privileges. Real modifications run under the administrator’s PostgreSQL permissions.
Plans are per administrator and expire after 20 minutes by default. You can also call cancel_plan. No schema change is made at the planning stage.
Optional static hosting tools
Set Standalone deployment to start the Nginx static host and expose the six site_* tools. Every authenticated user can manage only the folder associated with their verified PostgreSQL username. Projects may have nested css/, js/, assets/ and other allowed paths.
Uploaded files are public to visitors who can access the static URL. There is no per-viewer authentication on Nginx in this version. Creating or updating a site does not grant browser-side access to PostgreSQL.
Legacy REST helpers
REST_MCP_TOOLS=false by default. When explicitly enabled, Axiomony exposes three PostgREST helper tools for existing integrations. These tools do not replace database authorization, and new task-specific AI-generated applications should prefer Data MCP through a trusted runtime.