workboard_update_user_tool
AI agents use workboard_update_user_tool to create or update resources in MCP Workboard — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Workboard environment.
This tool updates user records, which is a reversible modification operation. Without a description, we rely on the naming convention: 'update_user' clearly maps to Write rather than Read (no 'get'), Destructive (no 'delete'), Execute (no 'run'/'execute'), or Financial.
From the tool's definition Tool name is 'workboard_update_user_tool' which explicitly indicates modification of user data. The 'update' verb combined with 'user' scope indicates a write operation that creates or modifies data reversibly.
Attacks that exploit this kind of access
workboard_update_user_tool. 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_user_tool: 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_user_tool 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_user_tool 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_user_tool. 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_user_tool 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →