add_incident_update · Pingera MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_incident_update does on Pingera MCP Server

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

WHY IT NEEDS A POLICY

Why add_incident_update needs a policy

The tool appears to create or append data to incident records (reversible operation typical of Write category). While the description is empty, the sibling tools on this server (create_incident, create_alert, create_check) are all Write/Create operations, and this tool follows that pattern.

From the tool's definition Tool name 'add_incident_update' indicates appending/creating an update record to an incident. The verb 'add' combined with 'incident_update' suggests creating or modifying incident data. No description provided, lowering confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_incident_update Rate-limited

add_incident_update 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": {
    "add_incident_update": {
      "limits": [
        {
          "counter": "add_incident_update_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 Pingera MCP Server, so you can run agents against it safely.

FAQ

Questions about add_incident_update

What does the add_incident_update tool do? +

add_incident_update. It is categorised as a Write tool in the Pingera MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_incident_update? +

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

What risk level is add_incident_update? +

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

Can I rate-limit add_incident_update? +

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

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

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