26 tools from the Peaka MCP Server, categorised by risk level.
View the Peaka policy →peaka_get_cache_statuses Get all cache statuses for tables in the Peaka project. Returns the current caching state, execution history, and progress for each cached table.
... peaka_get_connection_detail Get connection-specific configuration detail for a data source connection in the Peaka project. The response shape varies by connection type — only... peaka_get_metadata_refresh_status Check the current status of a metadata refresh job for a specific catalog. Possible statuses: NOT_ACTIVE, COMPLETED, WAITING, ACTIVE, DELAYED, FAIL... peaka_get_project_metadata Get metadata for all catalogs, schemas, and tables in the Peaka project in a single call. Optionally filter by catalogId and/or schemaName. Use thi... peaka_get_relations Get table relationships (foreign keys) for a catalog in the Peaka project. Useful for understanding how tables connect when constructing JOINs — wi... peaka_get_table_statistics Get column-level statistics for a table in the Peaka project. Returns the catalog/schema/table identifiers and a per-column distinctFraction (estim... peaka_list_catalogs List all available catalogs in the Peaka project. Returns catalog names, types, and connection info.
If you do not already know the projectId ... peaka_list_columns List all columns for a given table in the Peaka project. Returns column names, data types, and constraints. Use peaka_get_project_metadata first to... peaka_list_connections List all data source connections in the Peaka project. Returns each connection's id, name, type, and (for OAuth-based connections) callback URL. Us... peaka_list_projects List all projects accessible for the user. Use this tool to discover projectIds, then pass the chosen projectId to subsequent tool calls. peaka_list_queries List all saved queries in the Peaka project. Returns query names, SQL content, and whether they are plain or materialized.
If you do not alrea... peaka_list_schemas List all available schemas for a given catalog in the Peaka project.
If you do not already know the projectId for the current task, call peaka... peaka_list_tables List all available tables for a given catalog and schema in the Peaka project.
If you do not already know the projectId for the current task, ... peaka_query_golden_sqls Query question/sql pairs from Peaka's golden sql vector store.
If you find an existing query matching the user's question, just use it.
Oth... peaka_refresh_project_metadata Refresh project metadata for a specific catalog. This is a long-running operation that should only be used when a data source has structurally chan... peaka_create_cache Create a cache for a table in the Peaka project. Caching a table improves query performance by storing the data locally. Schedule expressions are o... peaka_create_cache_batch Create caches for multiple tables in a single call. Use this instead of repeated peaka_create_cache calls when caching many tables — it avoids part... peaka_create_query Create a named, saved query in the Peaka project's semantic layer. Returns the created query object including its ID, which can be passed to peaka_... peaka_update_cache Update cache settings on an existing cache in the Peaka project. This endpoint replaces — not merges — the schedules, so both incrementalSchedule a... peaka_update_query Update an existing saved query in the Peaka project. Adjusts the display name and/or SQL body. At least one of displayName or inputQuery must be pr... peaka_delete_cache Delete an existing cache in the Peaka project. Removes the cache entirely; the underlying table is not affected. Use the cacheId returned from peak... peaka_delete_query Delete a saved query from the Peaka project. Use the queryId returned from peaka_list_queries.
If you do not already know the projectId for th... peaka_execute_query Execute a saved query by its ID in the Peaka project. Use peaka_list_queries to find available query IDs.
If you do not already know the proje... peaka_execute_sql_query Runs the given sql query on Peaka.
BEFORE RUNNING THIS TOOL:
1: Use peaka_get_project_metadata to determine which tables should be used ... peaka_refresh_cache_full Trigger a full refresh on an existing cache in the Peaka project. Use the cacheId returned from peaka_get_cache_statuses.
If you do not alread... peaka_refresh_cache_incremental Trigger an incremental update on an existing cache in the Peaka project. Fetches only new/changed rows — much faster than a full refresh. Use the c... The Peaka MCP server exposes 26 tools across 4 categories: Read, Write, Destructive, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Peaka server.
Peaka tools are categorised as Read (15), Write (5), Destructive (2), Execute (4). Each category has a recommended default policy.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.