AI agents use create_work_log to create or update resources in Plane — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Plane environment.
Work log creation modifies project tracking data by adding a new log entry. This is a reversible write operation that creates data without deleting, destroying, or executing arbitrary code. The severity is medium because misuse could clutter project records or log false time entries, but the blast radius is limited to project management data, not code execution or data destruction.
From the tool's definition Tool name is 'create_work_log' indicating creation of a new work log entry; sibling tools include create_cycle, create_initiative, create_label, create_module which are all Write operations; description is empty, limiting direct evidence
Attacks that exploit this kind of access
create_work_log. It is categorised as a Write tool in the Plane MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Plane MCP server in PolicyLayer and add a rule for create_work_log: 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 Plane. Nothing to install.
create_work_log 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_work_log 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_work_log. 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_work_log is provided by the Plane MCP server (@makeplane/plane-mcp-server). 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 →