AI agents use assign_action_item_supervisor to create or update resources in JoeMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your JoeMCP environment.
The tool creates or modifies data (assigning a supervisor to an action item) without permanently deleting or destroying information. This is a typical Write operation. Severity is medium because supervisory assignments in a construction management system could affect project accountability and task tracking, but the change is reversible and has no financial impact or destructive consequences.
From the tool's definition Tool description states 'Assign a supervisor to an action item' — this modifies an existing action item by assigning a supervisor, a reversible data change.
Attacks that exploit this kind of access
Assign a supervisor to an action item. It is categorised as a Write tool in the JoeMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Joe MCP server in PolicyLayer and add a rule for assign_action_item_supervisor: 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 JoeMCP. Nothing to install.
assign_action_item_supervisor 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 assign_action_item_supervisor 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 assign_action_item_supervisor. 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.
assign_action_item_supervisor is provided by the Joe MCP server (lumberjack-so/joemcp). 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 →