AI agents use update_project_member_role to create or update resources in Tickr — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tickr environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
role | string | Yes | New project role |
project | string | Yes | Project slug |
user_id | string | Yes | UUID of the user |
Parameters from the server's own tool schema.
This is a Write operation because it modifies project member metadata (role assignment) reversibly. Severity is medium because incorrect role changes could grant unintended permissions or remove necessary access, affecting team collaboration and security posture. It's not Destructive because role changes are reversible (the member still exists, their role can be changed again).
From the tool's definition Tool name is 'update_project_member_role' and description states it 'Update[s] the role of a project member'. This modifies an existing project member's role/permissions, which is a reversible data change.
Attacks that exploit this kind of access
Update the role of a project member. It is categorised as a Write tool in the Tickr MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_project_member_role accepts 3 parameters: role, project, user_id. Required: role, 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 update_project_member_role: 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.
update_project_member_role 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 update_project_member_role 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 update_project_member_role. 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.
update_project_member_role 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 →