update_insight_status

SERVERDoit SOURCE@doitintl/doit-mcp-server

Medium RISK CLASS

Category Write

Parameters 42 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/doit/update-insight-status.md

WHAT IT DOES

What update_insight_status does on Doit

AI agents use update_insight_status 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
`key`	string	Yes	The unique key identifying the insight to update.
`source`	string	—	The source that owns the insight. Only 'public-api' insights can be managed via this endpoint; defaults to public-api.
`status`	string	Yes	The new display status of the insight. Possible values: actionable, acknowledged, optimized, dismissed, in progress.
`dismissalDetails`	object	—	Details for why the insight was dismissed; reason is required when status is 'dismissed'.

Parameters from the server's own tool schema.

RISK

Why update_insight_status is rated Medium

An AI agent can call update_insight_status 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 update_insight_status 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 update_insight_status, this is the rule to start with:

update_insight_status Rate-limited

update_insight_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": {
    "update_insight_status": {
      "limits": [
        {
          "counter": "update_insight_status_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 update_insight_status call is checked against it from then on.

FAQ

Questions about update_insight_status

What does the update_insight_status tool do? +

Use this when the user wants to change the display status of an existing insight (e.g. mark it acknowledged, in progress, optimized, or dismissed). This endpoint is deprecated but remains the safe choice for status-only changes because it preserves optional insight metadata; post_insight_result replaces it. Only insights owned by the 'public-api' source can be managed. When dismissing, dismissalDetails.reason is required; comment is optional. Do NOT use this to edit an insight's title/description or create one (use post_insight_result). 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 update_insight_status accept? +

update_insight_status accepts 4 parameters: key, source, status, dismissalDetails. Required: key, status. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_insight_status? +

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

What risk level is update_insight_status? +

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

Can I rate-limit update_insight_status? +

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

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

update_insight_status 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

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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