peaka_create_semantic_catalog · Peaka MCP: Risk & Policy

WHAT IT DOES

What peaka_create_semantic_catalog does on Peaka

AI agents use peaka_create_semantic_catalog to create or update resources in Peaka — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Peaka environment.

WHY IT NEEDS A POLICY

Why peaka_create_semantic_catalog needs a policy

The tool creates a new semantic catalog (a namespace grouping semantic tables) in the Peaka project. This is a Write operation because it modifies the project structure by adding a new catalog, but the action is reversible (can be deleted via peaka_delete_semantic_table or similar operations).

From the tool's definition Tool name contains 'create' and description states 'Create a semantic catalog' — this is a reversible data modification operation that creates a new catalog resource.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

peaka_create_semantic_catalog Rate-limited

peaka_create_semantic_catalog stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "peaka_create_semantic_catalog": {
      "limits": [
        {
          "counter": "peaka_create_semantic_catalog_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Peaka, so you can run agents against it safely.

FAQ

Questions about peaka_create_semantic_catalog

What does the peaka_create_semantic_catalog tool do? +

Create a semantic catalog in the Peaka project. A semantic catalog groups semantic tables — saved queries surfaced as queryable tables — under a single namespace. Returns the created catalog including its id. ${PROJECT_ID_HINT}. It is categorised as a Write tool in the Peaka MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on peaka_create_semantic_catalog? +

Register the Peaka MCP server in PolicyLayer and add a rule for peaka_create_semantic_catalog: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Peaka. Nothing to install.

What risk level is peaka_create_semantic_catalog? +

peaka_create_semantic_catalog is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit peaka_create_semantic_catalog? +

Yes. Add a rate_limit block to the peaka_create_semantic_catalog rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block peaka_create_semantic_catalog completely? +

Set action: deny in the PolicyLayer policy for peaka_create_semantic_catalog. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides peaka_create_semantic_catalog? +

peaka_create_semantic_catalog is provided by the Peaka MCP server (@peaka/mcp-server-peaka). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.