Update key result progress for OKR check-ins
Risk signalsModifies OKR progress metrics
Part of the MCP Workboard server.
Free to start. No card required.
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.
Without a policy, an AI agent could call workboard_update_key_result repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach MCP Workboard.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"workboard_update_key_result": {
"limits": [
{
"counter": "workboard_update_key_result_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full MCP Workboard policy for all 17 tools.
These attack patterns abuse exactly the kind of access workboard_update_key_result gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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.
Register the MCP Workboard MCP server in PolicyLayer and add a rule for workboard_update_key_result: 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 MCP Workboard. Nothing to install.
workboard_update_key_result is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the workboard_update_key_result 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.
Set action: deny in the PolicyLayer 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.
workboard_update_key_result is provided by the MCP Workboard MCP server (mcp-workboard-crunchtools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 MCP Workboard tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.