Delete an existing cache in the Peaka project. Removes the cache entirely; the underlying table is not affected. 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 projec...
Part of the Peaka MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents may call peaka_delete_cache to permanently remove or destroy resources in Peaka. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call peaka_delete_cache in a loop, permanently destroying resources in Peaka. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
tools:
peaka_delete_cache:
rules:
- action: deny
reason: "Blocked by default — enable with approval"See the full Peaka policy for all 26 tools.
Agents calling destructive-class tools like peaka_delete_cache have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.
peaka_delete_cache is one of the critical-risk operations in Peaka. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.
Delete an existing cache in the Peaka project. Removes the cache entirely; the underlying table is not affected. 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 Destructive tool in the Peaka MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Add a rule in your Intercept YAML policy under the tools section for peaka_delete_cache. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Peaka MCP server.
peaka_delete_cache is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the peaka_delete_cache 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_delete_cache. 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_delete_cache 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.