peaka_refresh_materialized_query · Peaka MCP: Risk & Policy

WHAT IT DOES

What peaka_refresh_materialized_query does on Peaka

AI agents invoke peaka_refresh_materialized_query to trigger actions in Peaka. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why peaka_refresh_materialized_query needs a policy

This tool triggers a refresh operation on a materialized query, which re-executes the underlying query and overwrites the cached/materialized result. This is an Execute-category action as it runs an external operation whose effects depend on the query being refreshed. It is not purely destructive (old data is replaced with fresh data, not permanently lost), and not a simple read or write.

From the tool's definition 'Trigger a refresh on a materialized saved query' — actively triggers an external operation (materialized view refresh) in the Peaka project

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

peaka_refresh_materialized_query Rate-limited

peaka_refresh_materialized_query stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_refresh_materialized_query": {
      "limits": [
        {
          "counter": "peaka_refresh_materialized_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_refresh_materialized_query

What does the peaka_refresh_materialized_query tool do? +

Trigger a refresh on a materialized saved query in the Peaka project. Use the queryId returned from peaka_list_queries for queries whose queryType is. It is categorised as a Execute tool in the Peaka MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on peaka_refresh_materialized_query? +

Register the Peaka MCP server in PolicyLayer and add a rule for peaka_refresh_materialized_query: 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_refresh_materialized_query? +

peaka_refresh_materialized_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit peaka_refresh_materialized_query? +

Yes. Add a rate_limit block to the peaka_refresh_materialized_query 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_refresh_materialized_query completely? +

Set action: deny in the PolicyLayer policy for peaka_refresh_materialized_query. 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_refresh_materialized_query? +

peaka_refresh_materialized_query 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.