List reported needs, optionally filtered by category.
AI agents call list_needs to retrieve information from Report Needs MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays data about reported needs without modifying, deleting, or executing operations. The optional filtering parameter is a standard read query feature. The blast radius of misuse is minimal — an agent could only access information already in the system. This is a straightforward Read category tool.
From the tool's definition Tool name is 'list_needs' and description states 'List reported needs, optionally filtered by category' — a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
List reported needs, optionally filtered by category. It is categorised as a Read tool in the Report Needs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Report Needs MCP Server MCP server in PolicyLayer and add a rule for list_needs: 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.
list_needs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_needs 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 list_needs. 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.
list_needs 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 →