AI agents use add_project_item to create or update resources in Mcp Gmail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Gmail environment.
This tool creates/modifies project state by adding items, making it a Write action. Severity is medium because misuse could clutter or disorganize GitHub projects, but the operation is reversible and does not delete data or execute arbitrary code. Note: The server claims to be 'Mcp Gmail' but exposes GitHub-related tools; this may indicate miscategorization or a multi-service server.
From the tool's definition Tool description states 'Add an issue or pull request to a GitHub project', which modifies a GitHub project by adding items. This is a reversible write operation—items can be removed from projects.
Attacks that exploit this kind of access
Add an issue or pull request to a GitHub project. It is categorised as a Write tool in the Mcp Gmail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Gmail MCP server in PolicyLayer and add a rule for add_project_item: 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 Mcp Gmail. Nothing to install.
add_project_item 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 add_project_item 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 add_project_item. 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.
add_project_item is provided by the Mcp Gmail MCP server (@monsoft/mcp-gmail). 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 →