Remove a member from a project
AI agents call remove_project_member to permanently remove resources in Tickr — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
project | string | Yes | Project slug |
user_id | string | Yes | UUID of the user to remove |
Parameters from the server's own tool schema.
Removing a member from a project revokes their access and associated permissions. While not data deletion, it is an irreversible action (or at least one with significant consequences) that could disrupt collaboration and is not simply a write/update. It falls under Destructive as it permanently removes an entity's association with the project.
From the tool's definition 'Remove a member from a project' — removal of project membership is an irreversible access change that cannot be trivially undone
Attacks that exploit this kind of access
Remove a member from a project. It is categorised as a Destructive tool in the Tickr MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_project_member accepts 2 parameters: project, user_id. Required: project, user_id. The full parameter table on this page comes from the server's own tool schema.
Register the Tickr MCP server in PolicyLayer and add a rule for remove_project_member: 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 Tickr. Nothing to install.
remove_project_member is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_project_member 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 remove_project_member. 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.
remove_project_member is provided by the Tickr MCP server (@k-system/tickr-mcp). 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 →