Add a member to a Dooray project
AI agents use dooray_add_project_member to create or update resources in Dooray MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dooray MCP Server environment.
This tool creates or modifies project membership data by adding a member to a project. This is a reversible Write operation (the member could theoretically be removed later). It does not execute arbitrary code (Execute), destroy data irreversibly (Destructive), or involve financial transactions (Financial).
From the tool's definition Tool name is 'dooray_add_project_member' and description states 'Add a member to a Dooray project' — this creates a new membership association, modifying project membership state.
Attacks that exploit this kind of access
Add a member to a Dooray project. It is categorised as a Write tool in the Dooray MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dooray MCP Server MCP server in PolicyLayer and add a rule for dooray_add_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 Dooray MCP Server. Nothing to install.
dooray_add_project_member 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 dooray_add_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 dooray_add_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.
dooray_add_project_member is provided by the Dooray MCP Server MCP server (kwanok/dooray-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 →