search_reports

A read tool on the Nitrostack MCP server.

SERVERNitrostack SOURCEnitrocloudofficial/nitrostack

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nitrostack/search-reports.md

WHAT IT DOES

What search_reports does on Nitrostack

AI agents call search_reports to retrieve information from Nitrostack without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why search_reports is rated Low

Search operations retrieve and query existing data without side effects. Even though the tool description is empty, the naming convention and the context of sibling tools (all read operations for retrieving bug bounty and report data) strongly indicate this is a query/search function. No data is created, modified, deleted, or executed—only queried.

From the tool's definition Tool name 'search_reports' indicates a search operation. The verb 'search' is characteristically a read-only action that retrieves or queries data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_reports safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_reports, this is the rule to start with:

search_reports Allowed

search_reports is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_reports": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nitrostack, apply this rule, and every search_reports call is checked against it from then on.

FAQ

Questions about search_reports

What does the search_reports tool do? +

search_reports is a read tool on the Nitrostack MCP server. It is categorised as a Read tool in the Nitrostack MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_reports? +

Register the Nitrostack MCP server in PolicyLayer and add a rule for search_reports: 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 Nitrostack. Nothing to install.

What risk level is search_reports? +

search_reports is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_reports? +

Yes. Add a rate_limit block to the search_reports 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 search_reports completely? +

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

search_reports is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nitrostack, and thousands of servers like it.

This server

All 697 Nitrostack tools →

Across the catalogue

evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →