konsulto_bulk_update_status · Konsulto MCP: Risk & Policy

WHAT IT DOES

What konsulto_bulk_update_status does on Konsulto

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

WHY IT NEEDS A POLICY

Why konsulto_bulk_update_status needs a policy

This tool modifies audit findings' status fields in the Konsulto platform. While reversible (status can be changed again), bulk operations affect multiple records simultaneously, increasing risk of unintended state changes.

From the tool's definition Tool description states: 'Change the status of many findings at once.' The verb 'change' indicates modification of data (finding status). The bulk nature ('many findings at once') amplifies the blast radius compared to single updates.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

konsulto_bulk_update_status Rate-limited

konsulto_bulk_update_status 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": {
    "konsulto_bulk_update_status": {
      "limits": [
        {
          "counter": "konsulto_bulk_update_status_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 Konsulto, so you can run agents against it safely.

FAQ

Questions about konsulto_bulk_update_status

What does the konsulto_bulk_update_status tool do? +

Change the status of many findings at once. Use for. It is categorised as a Write tool in the Konsulto MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on konsulto_bulk_update_status? +

Register the Konsulto MCP server in PolicyLayer and add a rule for konsulto_bulk_update_status: 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 Konsulto. Nothing to install.

What risk level is konsulto_bulk_update_status? +

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

Can I rate-limit konsulto_bulk_update_status? +

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

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

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