patch_anomaly

SERVERDoit SOURCE@doitintl/doit-mcp-server

Medium RISK CLASS

Category Write

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/doit/patch-anomaly.md

WHAT IT DOES

What patch_anomaly does on Doit

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

Parameter	Type	Required	Description
`id`	string	Yes
`customerContext`	string	—	Scope the request to a specific customer by ID. Required for DoiT employees (whose token isn't tied to a single customer); omit for direct customer users.
`customerFeedback`	object	Yes	Partial review-status update. Fields that are omitted are left unchanged. `reviewStatus` drives the state machine; `resolution` and `resolutionNote` apply only

Parameters from the server's own tool schema.

RISK

Why patch_anomaly is rated Medium

An AI agent can call patch_anomaly faster than any human can review: one bad instruction and it creates or modifies resources in Doit by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs patch_anomaly safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Doit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For patch_anomaly, this is the rule to start with:

patch_anomaly Rate-limited

patch_anomaly 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": {
    "patch_anomaly": {
      "limits": [
        {
          "counter": "patch_anomaly_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Doit, apply this rule, and every patch_anomaly call is checked against it from then on.

FAQ

Questions about patch_anomaly

What does the patch_anomaly tool do? +

Monitor cost spikes in your cloud environment. Updates the review status of the anomaly identified by {id}, the same identifier getAnomaly accepts. Mirrors the review workflow available in the console: set reviewStatus, and when resolving, qualify it with resolution and optionally a resolutionNote (feedback reason and comment). The change is recorded in the anomaly's review history exactly like a console update, and the actor is derived from the API credentials - never from the request body. Validation: reviewStatus is one of NEEDS_REVIEW, UNDER_REVIEW, RESOLVED; resolution (ANOMALY_CONFIRMED or NOT_ANOMALY) is required when reviewStatus is RESOLVED and forbidden otherwise; resolutionNote.reason must belong to the given resolution - SECURITY_BREACH, MISCONFIGURATION, UNINTENTIONAL_PROVISIONING, EXPECTED_COST_SPIKE or ANOMALOUS_OTHER for ANOMALY_CONFIRMED, and FAULTY_ANOMALY_DETECTION_MODEL, INCORRECT_DATA, LOW_IMPACT or NON_ANOMALOUS_OTHER for NOT_ANOMALY. Requires the AnomaliesManager permission and DoiT API access (platform:externalApi). It is categorised as a Write tool in the Doit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does patch_anomaly accept? +

patch_anomaly accepts 3 parameters: id, customerContext, customerFeedback. Required: id, customerFeedback. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on patch_anomaly? +

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

What risk level is patch_anomaly? +

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

Can I rate-limit patch_anomaly? +

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

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

patch_anomaly is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Doit, and thousands of servers like it.

This server

All 238 Doit tools →

Across the catalogue

propose_patch on 0sec → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →