AI agents use create_project_note_comment to create or update resources in Repsona — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Repsona environment.
This tool creates new data (a comment) within an existing project note structure. It is reversible (comments can typically be deleted, as evidenced by the sibling tool 'delete_project_note_comment'). Therefore it falls under Write category. Severity is medium because misuse could spam or clutter project notes, but the blast radius is limited to a single project's note comments and the action is reversible.
From the tool's definition Tool creates a comment on a project note: 'create_project_note_comment' and description states it posts comments ('コメントを投稿します') to notes within a specified project.
Attacks that exploit this kind of access
指定したプロジェクト内のノートにコメントを投稿します. It is categorised as a Write tool in the Repsona MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Repsona MCP server in PolicyLayer and add a rule for create_project_note_comment: 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 Repsona. Nothing to install.
create_project_note_comment 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 create_project_note_comment 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 create_project_note_comment. 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.
create_project_note_comment is provided by the Repsona MCP server (@bellx2/repsona-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 →