AI agents use plane-workspace-invite 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.
This tool creates a new workspace invitation and assigns a role to the invitee, which modifies workspace membership state reversibly. The ability to invite users with varying privilege levels (especially Admin at role 20) and grant access to projects represents a significant write operation that alters workspace permissions.
From the tool's definition Invite a user to the workspace by email. They must accept the invite before they can be added to projects. Role: 5=Guest, 10=Viewer, 15=Member, 20=Admin.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Invite a user to the workspace by email. They must accept the invite before they can be added to projects. Role: 5=Guest, 10=Viewer, 15=Member, 20=Admin. 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 plane-workspace-invite: 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.
plane-workspace-invite 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 plane-workspace-invite 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 plane-workspace-invite. 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.
plane-workspace-invite is provided by the Plane MCP server (philipvanlewis/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 →