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 cacheId returned from peaka_get_cache_statuses. If you do not already know the projectId for the current task, call peaka_list_projects first and ...
Part of the Peaka MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke peaka_refresh_cache_incremental to trigger processes or run actions in Peaka. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
peaka_refresh_cache_incremental can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
peaka_refresh_cache_incremental:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Peaka policy for all 26 tools.
Agents calling execute-class tools like peaka_refresh_cache_incremental have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
peaka_refresh_cache_incremental is one of the high-risk operations in Peaka. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
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 cacheId returned from peaka_get_cache_statuses. If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.. 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.
Add a rule in your Intercept YAML policy under the tools section for peaka_refresh_cache_incremental. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Peaka MCP server.
peaka_refresh_cache_incremental is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the peaka_refresh_cache_incremental rule in your Intercept 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.
Set action: deny in the Intercept policy for peaka_refresh_cache_incremental. 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.
peaka_refresh_cache_incremental is provided by the Peaka MCP server (@peaka/mcp-server-peaka). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.