AI agents use import_work_item_types_to_project 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.
The tool performs a bulk import operation that modifies project structure by adding work item types. This is a Write action (creates/modifies data reversibly) rather than Read (no query-only function evident from name) or Destructive (import is reversible; types can be removed). Severity is medium because misconfiguration could affect project workflow but doesn't irreversibly delete data or move finances.
From the tool's definition Tool name 'import_work_item_types_to_project' indicates creation or modification of project configuration via bulk import operation. Description is empty, limiting precision.
Attacks that exploit this kind of access
import_work_item_types_to_project. 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 import_work_item_types_to_project: 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.
import_work_item_types_to_project 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 import_work_item_types_to_project 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 import_work_item_types_to_project. 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.
import_work_item_types_to_project 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 →