Create a new Action Item. Can be Generic (ActionTypeId=3), Cost Change (ActionTypeId=1), or Schedule Change (ActionTypeId=2). For Cost/Schedule changes, you MUST include the corresponding nested object with all required fields.
AI agents use create_action_item 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.
This tool creates new records (action items) in the JoeAPI system, which is a reversible write operation. It does not execute arbitrary code, delete data, or move financial resources directly—though Cost Change and Schedule Change action items may have downstream financial/scheduling implications, the tool itself only creates metadata records.
From the tool's definition Tool name 'create_action_item' and description 'Create a new Action Item' explicitly indicate data creation.
Attacks that exploit this kind of access
Create a new Action Item. Can be Generic (ActionTypeId=3), Cost Change (ActionTypeId=1), or Schedule Change (ActionTypeId=2). For Cost/Schedule changes, you MUST include the corresponding nested object with all required fields. 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 create_action_item: 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.
create_action_item 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 create_action_item 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 create_action_item. 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.
create_action_item 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 →