Skip to content
Axiomony documentation

MCP tool reference

Search the complete tool catalog and see exactly who can access each capability.

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.

23 of 23 tools shown
ToolGroupWhat it doesRequired permissionsAvailable when
whoamiCoreShow the current PostgreSQL account and broad available operation categories.Authenticated PostgreSQL loginAlways visible
list_tablesCoreList accessible tables and their table-level privileges.Authenticated login; results limited by database permissionsAlways visible
describe_tableCoreInspect accessible columns, types, descriptions and effective column privileges.Authenticated login; relevant relation/column accessAlways visible
explain_permissionsCoreInspect grants, RLS policies, triggers and constraints; optionally probe SELECT visibility. Cannot prove arbitrary writes will succeed.Authenticated login; any SELECT probe still requires database privilegesAlways visible
app_integration_guideCoreExplain Data-MCP integration for AI-generated forms, reports and dashboards.Authenticated PostgreSQL loginAlways visible
select_recordsDataSelect filtered rows, with ordering and a result limit up to 100.Relevant SELECT privileges; RLS appliesWhen user has SELECT somewhere
insert_recordDataInsert one record into an authorized table.INSERT on relevant columns; database rules applyWhen user has INSERT somewhere
update_recordsDataUpdate filtered rows; mandatory filters and max_rows 1–100 (default 20).UPDATE on target columns; relevant filter/SELECT rights; RLSWhen user has UPDATE somewhere
delete_recordsDataDelete filtered rows; mandatory filters and max_rows 1–100.DELETE on table; relevant filter/SELECT rights; RLSWhen user has DELETE somewhere
inspect_databaseAdminInspect actual PostgreSQL catalogs, schema objects, policies and functions.Superuser or mcp_admin; catalog visibility still appliesAdmin only
manage_databaseAdminGenerate 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 planningAdmin only
review_planAdminReturn a stored plan summary, warnings and proposed SQL for review.Same administrator and a valid pending plan IDAdmin only
implement_planAdminExecute a previously approved migration against PostgreSQL.Same administrator; valid plan ID; confirm=true; actual PostgreSQL DDL privilegesAdmin only
cancel_planAdminDiscard a pending migration without changing the database.Same administrator and a valid pending plan IDAdmin only
site_listHostingList the logged-in user’s published projects, subfolders, files and URLs.Authenticated PostgreSQL login; own files onlyStandalone deployment
site_read_fileHostingRead one of the user’s published files and its SHA-256 version hash.Authenticated login; own files onlyStandalone deployment
site_create_fileHostingPublish a new HTML/CSS/JS/static asset and create missing folders.Authenticated login; own user directory; quotas and allowed file typesStandalone deployment
site_update_fileHostingReplace an existing own file with SHA-256 concurrency protection.Authenticated login; own file and correct expected_sha256Standalone deployment
site_delete_fileHostingRemove an own file; optional expected SHA-256 verification.Authenticated login; own fileStandalone deployment
site_delete_projectHostingDelete an entire own published project and its files.Authenticated login; own project; confirm=trueStandalone deployment
rest_api_guideLegacy RESTDescribe legacy direct PostgREST integration and token flow. Not recommended for new generated apps.Authenticated PostgreSQL loginREST_MCP_TOOLS=true
rest_relationshipsLegacy RESTInspect readable table foreign-key relationships for REST queries.USAGE and appropriate SELECT on related structuresREST_MCP_TOOLS=true
generate_rest_requestLegacy RESTGenerate a REST URL, headers, filters and fetch example; does not execute the query.Corresponding SELECT/INSERT/UPDATE/DELETE and column rightsREST_MCP_TOOLS=true

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.

manage_databasePlan in memory
→
review_planInspect SQL
→
implement_planApprove & apply

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.