Medium Risk

vote_need

Upvote an existing need to signal that you also need this capability.

Part of the Report Needs server.

vote_need can modify Report Needs data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE REPORT NEEDS →

Free to start. No card required.

AI agents use vote_need to create or modify resources in Report Needs. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call vote_need repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Report Needs.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "vote_need": {
      "limits": [
        {
          "counter": "vote_need_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Report Needs policy for all 7 tools.

Get this rule live on your own Report Needs server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY REPORT NEEDS →

These attack patterns abuse exactly the kind of access vote_need gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so vote_need only ever does what you allow.

SECURE REPORT NEEDS →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the vote_need tool do? +

Upvote an existing need to signal that you also need this capability.. It is categorised as a Write tool in the Report Needs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on vote_need? +

Register the Report Needs MCP server in PolicyLayer and add a rule for vote_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. Nothing to install.

What risk level is vote_need? +

vote_need is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit vote_need? +

Yes. Add a rate_limit block to the vote_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.

How do I block vote_need completely? +

Set action: deny in the PolicyLayer policy for vote_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.

What MCP server provides vote_need? +

vote_need is provided by the Report Needs MCP server (eren-solutions/report-needs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Report Needs tool call.

Deterministic rules across all 7 Report Needs tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.