// SCAN REPORT

Peaka

26 tools. 11 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 6 May 2026

11 can modify or destroy data

15 read-only

26 tools total

// TOOL MAP

Read (15) Write / Execute (9) Destructive / Financial (2)

// WHAT CAN GO WRONG

Destructive tools (peaka_delete_cache, peaka_delete_query) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (peaka_create_cache, peaka_create_cache_batch, peaka_create_query) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (peaka_execute_query, peaka_execute_sql_query, peaka_refresh_cache_full) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

// RECOMMENDED RULES

Deny destructive operations

peaka_delete_cache:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

peaka_create_cache:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

peaka_get_cache_statuses:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

// ALL 26 PEAKA TOOLS

DESTRUCTIVE 2 tools

Destructive peaka_delete_cache Destructive peaka_delete_query

EXECUTE 4 tools

Execute peaka_execute_query Execute peaka_execute_sql_query Execute peaka_refresh_cache_full Execute peaka_refresh_cache_incremental

WRITE 5 tools

Write peaka_create_cache Write peaka_create_cache_batch Write peaka_create_query Write peaka_update_cache Write peaka_update_query

READ 15 tools

Read peaka_get_cache_statuses Read peaka_get_connection_detail Read peaka_get_metadata_refresh_status Read peaka_get_project_metadata Read peaka_get_relations Read peaka_get_table_statistics Read peaka_list_catalogs Read peaka_list_columns Read peaka_list_connections Read peaka_list_projects Read peaka_list_queries Read peaka_list_schemas Read peaka_list_tables Read peaka_query_golden_sqls Read peaka_refresh_project_metadata

// FAQ

Can an AI agent delete data through the Peaka MCP server? +

Yes. The Peaka server exposes 2 destructive tools including peaka_delete_cache, peaka_delete_query. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Peaka? +

The Peaka server has 5 write tools including peaka_create_cache, peaka_create_cache_batch, peaka_create_query. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the Peaka MCP server expose? +

26 tools across 4 categories: Destructive, Execute, Read, Write. 15 are read-only. 11 can modify, create, or delete data.

How do I add Intercept to my Peaka setup? +

One line change. Instead of running the Peaka server directly, prefix it with Intercept: intercept -c peaka.yaml -- npx -y @@peaka/mcp-server-peaka. Download a pre-built policy from policylayer.com/policies/peaka and adjust the limits to match your use case.

// RELATED SERVERS

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

Peaka

Other MCP servers with similar tools.

Let agents act without letting them run wild.