AI agents use create_task_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 a new comment attached to an existing task, which is a reversible write operation. It does not execute code, delete data, or perform financial transactions. The action is analogous to adding a comment in a project management system, which is a standard Write operation with minimal blast radius and low severity.
From the tool's definition Tool name: 'create_task_comment'; description translated: 'Post a comment to a specified task'. The verb 'create' indicates writing/creating new data.
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_task_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_task_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_task_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_task_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_task_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 →