workboard_update_key_result

Update key result progress for OKR check-ins

Modifies OKR progress metrics

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

mcp-workboard-crunchtools Write Risk 3/5

// WHEN AI AGENTS USE THIS TOOL

AI agents use workboard_update_key_result to create or modify resources in MCP Workboard. 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.

// WHY ENFORCE A POLICY ON WORKBOARD_UPDATE_KEY_RESULT

Without a policy, an AI agent could call workboard_update_key_result 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 MCP Workboard.

// RECOMMENDED POLICY

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

mcp-workboard.yaml

tools:
  workboard_update_key_result:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full MCP Workboard policy for all 17 tools.

// DETAILS

Tool Name workboard_update_key_result

Category Write

MCP Server MCP Workboard MCP Server

Risk Level Medium

// MORE MCP WORKBOARD TOOLS

Write workboard_create_objective Write workboard_create_user Write workboard_create_workstream Write workboard_update_user Write workboard_update_workstream Read Cross-platform Read Production-ready Read workboard_get_my_key_results

View all 17 tools →

// WHAT CAN GO WRONG

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

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

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

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the workboard_update_key_result tool do? +

Update key result progress for OKR check-ins. It is categorised as a Write tool in the MCP Workboard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on workboard_update_key_result? +

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

What risk level is workboard_update_key_result? +

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

Can I rate-limit workboard_update_key_result? +

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

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

workboard_update_key_result is provided by the MCP Workboard MCP server (mcp-workboard-crunchtools). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

workboard_update_key_result

Enforce policies on MCP Workboard