Mark a comment as resolved. Only the comment author can resolve it.
AI agents use resolve_comment to create or update resources in Rockhopper MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rockhopper MCP Server environment.
The tool performs a state change on a comment—marking it as resolved—which is a modification operation. This falls into the Write category because it creates or modifies data reversibly. The severity is low because resolving comments is a low-risk administrative action with minimal blast radius. The permission restriction ('Only the comment author can resolve it') further limits potential misuse.
From the tool's definition The tool description states 'Mark a comment as resolved,' which modifies the state of a comment object (reversibly, as comments can presumably be unresololved).
Attacks that exploit this kind of access
Mark a comment as resolved. Only the comment author can resolve it. It is categorised as a Write tool in the Rockhopper MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rockhopper MCP Server MCP server in PolicyLayer and add a rule for resolve_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 Rockhopper MCP Server. Nothing to install.
resolve_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 resolve_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 resolve_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.
resolve_comment is provided by the Rockhopper MCP Server MCP server (rockhopper-co/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 →