Medium Risk

peaka_update_query

Update an existing saved query in the Peaka project. Adjusts the display name and/or SQL body. At least one of displayName or inputQuery must be provided. 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. Reme...

Part of the Peaka MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use peaka_update_query to create or modify resources in Peaka. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call peaka_update_query repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Peaka.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

peaka.yaml
tools:
  peaka_update_query:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Peaka policy for all 26 tools.

Tool Name peaka_update_query
Category Write
MCP Server Peaka MCP Server
Risk Level Medium

View all 26 tools →

Agents calling write-class tools like peaka_update_query have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the peaka_update_query tool do? +

Update an existing saved query in the Peaka project. Adjusts the display name and/or SQL body. At least one of displayName or inputQuery must be provided. 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 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_update_query? +

Add a rule in your Intercept YAML policy under the tools section for peaka_update_query. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Peaka MCP server.

What risk level is peaka_update_query? +

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

Can I rate-limit peaka_update_query? +

Yes. Add a rate_limit block to the peaka_update_query 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.

How do I block peaka_update_query completely? +

Set action: deny in the Intercept policy for peaka_update_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_update_query? +

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

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.