Add context or details to an existing need.
AI agents use comment_need to create or update resources in Report Needs MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Report Needs MCP Server environment.
This is a Write operation because it modifies an existing need by appending comments/context. The modification is reversible (comments can typically be edited or removed separately). The severity is low because adding comments to infrastructure need reports has minimal blast radius—it cannot delete infrastructure, move funds, or cause cascading system failures.
From the tool's definition Tool name 'comment_need' and description 'Add context or details to an existing need' indicate the tool creates or appends new comment data to an existing record without deleting or destroying information.
Attacks that exploit this kind of access
Add context or details to an existing need. It is categorised as a Write tool in the Report Needs MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Report Needs MCP Server MCP server in PolicyLayer and add a rule for comment_need: 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 Report Needs MCP Server. Nothing to install.
comment_need 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 comment_need 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 comment_need. 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.
comment_need is provided by the Report Needs MCP Server MCP server (pypi:report-needs). 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 →